help test director - 1.0

Great tool for Agile Project Management, Test Management and Issue Tracking with powerful Integrations


# Homepage

# Introduction

# Welcome to TestDirector

Welcome to TestDirector Homepage.


This site contains 5 main parts:

1. Portal Menu - with the root structure of the whole TestDirector portal

2. Your tasks - you can see the tasks (filtered by priority or date) which are:

3. Your bugs - which can be filtered by priority or date

4. Watch box - with the following sections:

5. User menu - options for the individual user



# User Menu

# My profile

Under My Profile you can update your personal details, change your avatar and password.

On the right side you will see your assigned roles under specific projects.

# Projects

Your assignment under projects is displayed here with several filtering options.

# Logs

Every action you do in TestDirector is recorded in the Logs section. You can view your actions on this screen.

# Report problem

Should you experience any problem with TestDirector, please fill in the contact form and provide us with as much detailed issue explanation as possible.


# Help

This option will open our website with full guide of TestDirector where you will find possible solution to your problem or question.

# Language

Switch between the following languages:

# Schedule

# How to Use Schedule

# Create schedule

Management of your projects is important so this section allows you to create, edit and remove schedules based on your needs. 

Each Schedule can have any number of Projects in it. 


The first step to achieve this is to create a Schedule by hitting the "Create Schedule" button.

# View schedule

Click on the Schedule name to open detailed information in the Schedule Dashboard.




# Create report

Should you need the dashboard details to be exported, it is very easy to do.

Just click on the button "Report" at the top right corner of the dashboard and you'll get a PDF file with all the details.

# Design

Once you create an epic in Projects > Design section, you can link such epic into an existing Schedule in order to be able to track its progress, owner, amount of test cases and issues.

After you link the epics, you can view them on this screen.


# Edit schedule

For a better time management TestDirector offers you features such as creating milestones and iterations between them.

It's all helpful when you can see each milestone's description, deadlines and level of importance.

Be careful, if you would like to create Iteration you will need at least 2 milestones.


# Projects

# Introduction

# Create Project

There can be any number of projects in each Schedule.

To create your project, hit the button "Create project".

# View Archived Projects

Sometimes you will need to check your archived projects.

Those can be summoned by hitting the "Archive" button at the main Projects screen.

# Dashboard

# Dashboard

Dashboard displays the following areas of interest: 

  1. Tasks table reminds you of your upcoming activities  
  2. Bugs table allows you to track assigned items with their priority and status 
  3. Watch Box helps you keep track of your design 

# Design

# Design

Use the agile planning in your project by creating folders in which you will keep epics and stories.


For progress management you can edit your epics by linking them to a specific Schedule where you create milestones and iterations.

The new design also includes a summary of working hours estimation for all child stories, test analysis and test executions. All you have to do is add a work estimation in hours and time already spent while creating / editing the items.

To get to the screen below, click on the epic name in your folder.





The screen below shows the red sections which need to be filled in. In case of a test case, don't forget to assign an epic, story and a version.


# Test Plan

# Test Plan

Create a plan of your future tests by dividing it into test sprints and assigning test cases to specific users.

After clicking on either test plan or test sprint name, you get valuable details which you can see on the images below.


# Test Analysis

# Test Analysis

Test case creation has never been easier.

The analysis screen works based on a folder structure which should be created at the beginning.
Once you have a folder, you can start creating Test Sets and then Test Cases.

Other options of Test case creation:


Search and Filter sections are in place for better co-operation with a bigger amount of existing Test Sets/Cases.

# Test Execution

# Test Execution

Users with role permission to execute test cases will choose a Test Plan and a Test Sprint to see specific Test Cases.
Those can be opened and then executed by hitting the green play Timer button at the top center side of the screen.



Should any issues occur during the execution, user can immediately create a bug by hitting the "Issue" button (with a bug icon) on the failed scenario row.


# Issues

# Issues

Bugs created during a test case execution are being saved to this section.

You can always create a bug or a task here as well by using the Create Bug/Task button (use the green switch button to switch between Bugs and Tasks).

Tasks is a helpful feature to assign any task to any user in TestDirector.


# Settings

# General

Here you can edit initial information about the project. Change the name of your project and the description.


# Project roles

Assign specific roles to your coworkers for better management of your project.


# Ticketing system

Connection to 3rd party software (JIRA and GIT) for systems synchronization (these settings will configure TestDirector based on how e.g. JIRA names particular items).
More details for JIRA integration visit JIRA integration page


# Export

Select an area which you would like to export for detailed overview.


# Workflow

# Archive / Delete

You can archive or remove the current project. In case of removing, it will never be physically deleted as it will stay in our database in case you would need to revive the data.


# Tags

For better data organizing it's a good idea to use tags. In this section you can edit existing ones or create completely new tags.


# Activity

In order for users to track their time at work, create an activity to specific users and they will be able to use it in their Operating Log section.


# External Ticket

In case you have testers which don't have TestDirector license but you still need them to report any bugs from any application they are testing in a particular project, you may need this feature.

Fill in the Name of the form, select the mandatory sections and assign a person to receive the form messages.

Once you hit the Active checkbox, a URL link will appear. You can send it to your testers and whenever they create a bug in the form, the assigned person will receive a notification that there was a new bug created externally. This person can then create a bug in TestDirector and assign it for further processing.


# Issue

# How to Use Issue

# Introduction

All issues - bugs and tasks - across all projects are stored here with the following features:

# Create bug/task

Creating a new bug or task is easily done by hitting the "New" button at the top right corner of the screen.

Then select a project and type - bug, task or subtask.

# View bug/task

Once you click on the name of the bug or task, you get all the details.



# Users

# How to Use Users

# Introduction

Before you or other users could start using TestDirector, it is important to create user accounts.

Each user account will have specific roles assigned based on your needs.

This section gives you all features you need for effective user management.

# Create user

Create a new user by hitting the "Create user" button.

You will also need to assign specific user roles based on what the user is supposed to work with.

If you need different or more roles, head over to the portal menu for Settings > Specific section to configure your desired roles.

# Log

# How to Use Log

# Log check

Portal log section contains actions of all users. 

Use the filter option to search specific data based on your needs.

# Settings

# General Settings

# How to use

You can edit the following details in general settings:

Other details on the screen:


# Specific Settings

# Role

Add, edit or delete the roles based on your needs.

There are no limitations as to how you should name them or which rights to assign to them.


Once you hit the "Add role" button, you can decide whether the new role would be a portal one (giving the user specific rights in the whole portal) or a project one (user rights for a project).


# Mailer

Set email notifications to be sent to a user after a specific action happens, e.g. when you assign a test case to a user, he would receive an email with the content template which you created.

On this page you can see all the scenarios when an email notification can be sent.

Update the languages with your content, activate the email template and you're ready.




Should you need to use LDAP protocol to access and maintain your distributed directory information services, fill in the login details.

For any help with this feature, don't hesitate to contact our support team.


# Application list

For testing purposes to actually link the test with a particular application or system, it's important you create your application name list here.

First create modules and environments (next tabs in Settings) and then add your applications.


# Module

Add modules of the applications that will be tested.


# Environment

Add environments of the applications that will be tested.


# License

Once TestDirector is purchased, each owner receives a license key which is either prepopulated by Denevy or the owner can enter it himself.

TestDirector is checking the license validity with our license server and once the license expires, you will be notified.

License key is limited by an amount of users and time period based on the purchase.


# Broadcast message

When you need to notify all TestDirector users, you can use this feature which would add a highlighted message at the top of the TestDirector screen for everyone to see.

Set your message, highlight colour, when the message should appear and when it should end.



# Storage

# How to Use Storage

# Description

The backlog feature is stored in this section - you can create a folders with test sets and test cases and once you need them in a project, you simply copy them there.

Explanation for the following buttons:


# Reports

# How to Use Reports

# Description

Reports are very helpful and you can create your own here.

First create a report template which gets stored in the list of the main Reports page. Set your template with data you need.


Then use the function buttons to:



# Files

# How to Use Files

# Description

Every created folder, project or test case, everything is saved in a form of a file in the Files section.

There is no need to manipulate with the files.


# Import

# How to Use Import

# Description

Use the Import feature when you need to map your testing name structure or requirements structure into TestDirector.

All test sets, test cases and requirements are created automatically into a folder in the Storage.



After you export a mapping file from your other application (e.g. JIRA), create an import template for test cases.

In this template, fill in the excel columns from your mapping file which contain the data like test case name, etc.



After you export a mapping file from your other application (e.g. JIRA), create an import template for requirements.

In this template, fill in the excel columns from your mapping file which contain the data like status, epic, owner, etc.



Steps to complete the mapping and automatic creation:

Once these steps are completed, your folder in Storage section will contain newly created tests sets with test cases or reqirements.


# Operating Log

# How to Use Operating Log

# Reporting the working hours

Users will need to report how much time they spent working on their projects.

In order to do that, use this section to manage your working hours.

1. Hit the button "Operating log"

2. Fill in the form with following fields:

3. Once you save this form, a new line will appear at the Operating log screen.


# Technical Details

# What You Need to Know

# Hardware requierements



# Network requirements

TestDirector is using online verification of a license key.

It is required for the server where TestDirector is located to have access to domain

# Installation

  1. Download data from Denevy Git
  2. Set up configuration file
  3. Installation of additional files with the help from composer
  4. Load clean database with a default administrator account which is located in files/clear_db.sql
  5. Launch additional migrations for adding new sheets

# Configuration file

Config.local.production.neon file in folder app/Core/config serves for setting up and connecting the application to database.

Required fields:

It is possible to set sentry address in the configuration file for collecting potential issues for debug.

Enabling failure display is possible at app/bootstrap.php by changing $configurator->setDebugMode from false to true.

# Software Requirements



Apache or nginx config must be directed to public folder.

# System

# Help

# User guides

By hitting the Help menu section you will be redirected to our website user guides.

# JIRA Integration

# How to Use JIRA Integration

# Description

If you specifically need to integrate JIRA mapping into TestDirector, follow these steps:

  1. Create a JIRA account and find/create a project where you will perform testing and manage bugs/tasks
  2. Enter your JIRA login to TestDirector: Projects >> Settings >> Ticketing system.
    There are two ways on how to connect to JIRA in Connecting section - click on dropdown menu Issue tracking and choose one of the following options in the list:
      • Issue tracker: Jira (server)
      • URL address: root JIRA URL, e.g.
      • Project (Key): fill in the name of your project in capitals based on the JIRA project URL address

      • User: your JIRA username - these credentials are a default setting for connection to JIRA project (e.g. username: Testing Squad 1), if you need a specific login for you as a tester, your JIRA project will appear in My Profile settings (once you fill in your own JIRA credentials there, every bug and task created in TestDirector will get created in JIRA under your own JIRA account name and not under the general name e.g. Testing Squad 1)
      • Password: your JIRA password
      • NOTE: If you're using JIRA (server) and fill in a wrong password in TestDirector, JIRA understands it as an issue. You need to re-log in JIRA, check the "I'm not a robot" field and then fix the password in TestDirector.

      • Issue tracker: Jira (cloud)
      • URL address: root JIRA URL, e.g.
      • Project (Key): fill in the name of your project in capitals based on the JIRA project URL address
      • User: your JIRA username - these credentials are a default setting for connection to JIRA project (e.g. username: Testing Squad 1), if you need a specific login for you as a tester, your JIRA project will appear in My Profile settings (once you fill in your own JIRA credentials there, every bug and task created in TestDirector will get created in JIRA under your own JIRA account name and not under the general name e.g. Testing Squad 1)
      • API key: generate your own API key in JIRA cloud and enter it in here (JIRA guide here)

  3. Configure the JIRA mapping in TestDirector Mapping section below the Connecting section - once you log in via your credentials, TestDirector will provide dropdown lists with options from your JIRA project:
    • Use diacritics: this allows you to synchronize TestDirector with JIRA, using your bugs and tasks including diacritics within their names
    • Range of synchronization:
      • Full - there is no limitation, all bugs, tasks and sub-tasks will be synchronized to JIRA
      • Limited - restrict the synced items based on the label/tag which you enter in the field - the same label/tag name must be used in JIRA.
        To explain this further - all items in JIRA having the specific label/tag, which was configured in TestDirector, will be synced with TestDirector.
        On the other hand all items in TestDirector will be synced with JIRA even if there is no label/tag in them.


    • Issue Type - TestDirector will offer JIRA name options in the dropdown lists - select the correct JIRA name for a bug and a task

    • Priority - select the correct JIRA priority names to be mapped for TestDirector priorities (Low, Medium, High, Critical).
      NOTE: The number of priorities must be equal to those configured in JIRA project - configure your priorities in Project Settings >> Workflow >> Project - Priority


    • Bug states - select the correct JIRA names for bug status.
      NOTE: The number of bug states must be equal to those configured in JIRA project - configure your bug statuses in Project Settings >> Workflow >> Bugs - Statuses


    • Task states - select the correct JIRA names for task status.
      NOTE: The number of task states must be equal to those configured in JIRA project - configure your task statuses in Project Settings >> Workflow >> Tasks >> Statuses (button)


  4. Save your mapping.
  5. From now on, if you create a bug or a task in TestDirector, it will automatically get created in your JIRA project as well.

# Gitlab Integration

# How to connect gitlab with TestDirector

# Discription

If you specifically need to integrate GITLAB mapping into TestDirectorfollow these steps: 

  1. Create a GITLAB account and find/create a project where you will perform testing and manage bugs/tasks
  2. Enter your GITLAB login to TestDirectorProjects >> Settings >> Ticketing system. 
    Follow these steps to set up your GITLAB integration:
    • GITLAB:
      • Issue trackerGitLab (server)
      • URL addressroot GITLAB URL, e.g
      • Project (Key): fill in the name of your project in capitals based on the GITLAB project URL address 
      • User: your GITLAB username - these credentials are a default setting for connection to GITLAB project (e.gusername: Testing Squad 1), if you need a specific login for you as a tester, your GITLAB project will appear in My Profile settings (once you fill in your own GITLAB credentials thereevery bug and task created in TestDirector will get created in GITLAB under your own GITLAB account name and not under the general name e.g. Testing Squad 1) 
      • Passwordyour GITLAB password
  3. Configure the GITLAB mapping in TestDirector Mapping section below the Connecting section - once you log in via your credentialsTestDirector will provide dropdown lists with options from your GITLAB project:
    • Use diacriticsthis allows you to synchronize TestDirector with GITLABusing your bugs and tasks including diacritics within their names 
    • Range of synchronization: 
      • Full - there is no limitationall bugstasks and sub-tasks will be synchronized to GITLAB 
      • Limited - restrict the synced items based on the label/tag which you enter in the field - the same label/tag name must be used in GITLAB. 
        To explain this further - all items in GITLAB having the specific label/tag, which was configured in TestDirectorwill be synced with TestDirector. 
        On the other hand all items in TestDirector will be synced with GITLAB even if there is no label/tag in them. 
    • Issue Type - TestDirector will offer GITLAB name options in the dropdown lists - select the correct GITLAB name for a bug and a task 
    • Bug states - select the correct GITLAB names for bug status. 
      NOTE: The number of bug states must be equal to those configured in GITLAB project - configure your bug statuses in Project Settings >> Workflow >> Bugs - Statuses
    • Task states - select the correct GITLAB names for task status. 
      NOTE: The number of task states must be equal to those configured in GITLAB project - configure your task statuses in Project Settings >> Workflow >> Tasks >> Statuses (button)
  4. Save your mapping.
  5. From now on, if you create a bug or a task in TestDirectorit will automatically get created in your GITLAB project as well.