How to update and mail defects in Test Director?

Normal tracking of the defects requires too much efforts but tracking the repair of defects in a project just requires the periodic updates of the defects.

This can be done directly using either of the two:

1. Defects grid and
2. Defect details dialog box

However, the ability of both the methods to update some fields of the defects depends pretty much on the permission settings given by user. 

In this article we shall discuss how you can update the information of the defects by assigning different defects to different members of the development team, adding a comment and by changing the severity of the defects.

Steps for Updating Defects in test Director

1. Make sure that you have the defects module on display and if it is not do so by clicking on the defects tab.
2. Now, to update the defects directly using the defects grid, go to the defects grid and select the concerned defect that you also added using the ‘add new defects” dialog box. In order to assign the defect to a member, select the name of concerned member from the list by clicking on the ‘assigned to’ box in the defect  records.
3. Next click on the defect details tab and it will open up defect details dialog box for you.
4. In this defect details dialog box, do the following tasks:

a) Select the required severity from the severity box to change the severity level of the defect.

b)  Add a comment to explain the change in severity level if you wish so by clicking on the add comment button in the description menu.

5. To view all the attachments click on the attachments button in the left menu and you will see the list of URL attachments.
6. For viewing the history of the changes made to the defect click on the history button in the left menu. For every change made to the defect the date of the change, new value and name of the person who made the change is displayed by the test director.
7. When you are done with everything click OK to exit this dialog box and save the changes.

Steps to mail defects in Test Director

- The details about a defect can be shared with another user via e – mail. 

- With this, a routine of the inform development  and quality assurance can be developed regarding the defect repair activity.

- A ‘go to defect’ link is included in the test director using which the user can go directly to the concerned defect. 

- Follow the below mentioned steps to mail a defect to the concerned person:

1. First of all display the defects module by clicking on the defects tab.
2. Next select the defect you want to mail and click on the mail defects button. This will open up another dialog box called ‘send mail’ dialog box.
3. In this box you need to enter a valid e – mail address in the ‘To’ field.
4. For including any attachments or history of the defects select attachments and history option from the include box.
5. You can add your own comments under the additional comments.
6. When you are done composing the e – mail click on the send button. You will get a message box. Click ok.
7. The person to whom you have sent the mail can view it from his/ her mail box.

Even a test in the test plan can be associated with a specific defect in the defects grid. Whenever an association is created it can be determined whether the test is to be executed based up on the status of the defect. 

How to generate reports for analyzing the testing process in test director?

Reports and graphs in the test director testing process help you assess up to what extent have your requirements, test runs, test plans, defect tracking etc have progressed.

Generating Reports in Test Director

- In test director you have the facility of generating reports as well as graphs at any point of time in the testing process and from each of the test director modules. 

- You have the choice of working with the default settings as well as the customized ones. 

- While you customize the reports or the graphs you have the right to apply sort conditions as well as filters. 

- Also the information can be displayed according to your specifications if you wish so. 

- The settings you make can be saved as the favorite views and they can be reloaded whenever required. 

- A report can be generated from any of the modules of the test director. 

- Each module of the test director provides you with a variety of report generation options. 

- Once you have generated the report, you can customize various properties of the report as per your wish. 

- The information can be displayed according to your specifications by altering or customizing various properties of that report. 

In this article we shall provide you with the steps for generating a standard requirements report, customizing it for a specific user name and adding it to the favorites list.

Steps for generating reports in Test Director

Follow the steps mentioned below:

1. First step is to open your project and login. If the project is not open, log on to it.
2. To view the requirements tree you need to turn on the requirements module. To do so clicking on the requirements tab will display the requirements module.
3. Next step is to choose a report. To do so go to the analysis option, then reports, and then finally click on the standard requirements report. A report will open up containing the default data.
4. Next if you need to customize the report as per your needs and specifications.  Clicking on the configure report and sub reports button will launch a report customization page with all the default options already selected.
5. Here you will get various options for displaying the number of items per display page. Set the option to ‘all items in one page’ if you want them to be displayed all in one page.
6. If you want to define a filter to view the requirements that were created by a specific user name clicking on the set filter/ sort button will certainly help. A filter dialog box will open up where you will see a filed titled ‘author’. For this click the filter condition box and click on the browse button. This will again open up the select filter condition dialog box. For the users field select the test director log-in user name and click OK. This will close the select the filter condition dialog box. Once again click OK to close the filter dialog box.
7. Under fields specify the fields and order in which you want them to be displayed. Select the custom field layout and next click on the select fields button to open the select fields dialog box. You will observe the following two fields:

a) Available fields: fields that are not currently displayed.

b) Visible fields: fields that are currently displayed.

You need to select the attachment option in the visible fields box and click the left arrow in order to move it to the available fields. Move the required fields to the available fields box.

8. Clear the history.
9. You can add the report as a favorite view by clicking on the add to favorites button.
10. Close the report. 

How is test management done by the test director?

If you are familiar with all the concepts of the test director you can apply them to your software systems or applications since you know how it works.

The test director implements the test management via four major phases as mentioned below:

1. Specification of the requirements
2. Planning the tests
3. Execution of the tests
4. Tracking the defects

Throughout each of the phases the date can be analyzed by the detailed reports and graphs generated earlier. Firstly, you need to analyze your software system or application and determine all of your testing requirements. 

Phase I - specification of Requirements

The first phase of the test director test management process involves the following steps:

1. Examination of the documentation of the software system or application for the determining the testing scope i.e., test goals, strategies, objectives etc.
2. Building of a requirements tree for defining overall testing requirements.
3. Creation of a list of detailed testing requirements for each topic mentioned in the requirements tree.
4. Writing a description for each requirement, assigning a priority level to it and adding attachments if required.
5. Generation of the reports and graphs for providing assistance in the analyzation of the testing requirements.
6. Carrying out a review of the requirements to check if they meet the specifications.

Phase II - Planning the Tests

The second phase involves the following tasks:

1. Examination of the application, testing resources and system requirement for determining the test goals.
2. Division of the application in to modules to be tested and building of a test plan tree to divide the application in to testing units hierarchically.
3. Determination of the type of tests that are required for each module and adding a basic definition of each test to the test plan tree.
4. Linking each test to the corresponding testing requirement.
5. Developing manual tests where each test step describes the test operations and expected outcome. Deciding which tests are to be automated.
6. Creation of the test scripts for the tests that are to be automated using a custom testing tool such as mercury interactive testing tools.
7. Generation of the graphs and reports for the analyzation of the test planning data.
8. Reviewing the tests for determining their suitability to the testing goals.

Phase III - Execution of tests

Third phase involves the following activities:

1. Defining the tests in to groups so as to meet various testing goals of the project. This may involve testing a new version of the application or a specific function in it.
2. Deciding which all tests are to be included in the test set.
3. Scheduling the execution of the tests and assigning tasks to different application testers.
4. Execution of the tests either manually or automatically.
5. Viewing the results of the test runs for determining if a detect was detected in the application under test and generation of the reports and graphs for analyzation of the results.

Phase IV - Tracking the Defects

The last phase of the test management i.e., defect tracking involves the following activities:

1. Submitting new defects detected in the software system or application. Defects can be added during any phase by QA testers, project managers and developers etc.
2. Carrying out a review of the new defects and determining which ones are to be fixed.
3. Correcting the defects that were decided to be fixed.
4. Testing the new build of the software system or application and repeating the whole process until all the defects are fixed.
5. Generation of the graphs and reports to provide assistance in the analyzation of the progress of the defect fixes and determining the date when the application is to be released. 

How do you schedule and run tests in Test Director?

In this article we shall see how the tests can be scheduled and run. 

By configuring the conditions the test director can be instructed to postpone the run of the current test till the completion of some other specified tests is over. For example, the test b is scheduled to be run only after the test a finishes with the execution and there is one more test c which is scheduled to run only if the test b passes.

Also, the tests a and b can be scheduled to be executed a day prior to the execution of the test c. the tests and their conditions are displayed by the execution flow in the form of a diagram. 

Steps to schedule tests in test Director

Follow the below mentioned steps to schedule a test run:

1. Firstly, make sure that the test module is in the view mode and if it is  not then first enable it.
2. Second step involves creation of a new test. Click on the execution flow tab in the test lab module. Choose a folder in the test sets tree and click on the ‘new test set’ option. You will get a ‘new test set’ dialog box. Type in the following details:

a)   Test set name

b)   Description

Once you are done click OK and the test set will be added to the test sets tree in the left pane by the test director.

3. Add a test that you want to add to the test set created in the previous step. Using the ‘select tests’ button  to make the test director display the test plan tree in the right pane. Then, type the name of the test to be searched for in the find box in the test plan tree and click find button. Select the searched test and add it to the test set using the ‘add tests to test set’ button.
4. Any number of tests can be added to the test set. To add the tests to the execution flow either simply drag them in to the execution flow area or double click on them.
5. Add conditions using conditions tab. When you will click on the new button a ‘new execution condition’ dialog box will pop up. Select the required test and then passed option. This will instruct the test director to execute the next test only after the successful execution of the previous test. Click OK once done with this and the condition will be added to the run schedule of by the test director in the test dialog box.
6. You can even add a dependency condition to the tests by clicking on the time dependency tab. You will get a field titled ‘run at specified time’, in that specify the date of execution and click OK. Clicking on OK will close the run schedule. The conditions will be displayed by the test director in the execution flow area.
7. Further, if required, some execution condition can also be added to the tests.
8. For rearranging the tests in a hierarchical way, click on the perform layout option. You can then view the dependencies between the tests clearly.  

How the tests are run in Test Director?

We get two options form the test director namely:

a)   Running tests manually and

b)   Automating the tests.

Follow the steps below for the manual execution of a test:

1. Click on the test lab module to display the test lab module.
2. From the test sets select the required test set.
3. From the execution grid select the required test.
4. Clicking on the run will open up a manual runner dialog box.
5. To begin the test run click on the test run. Parameter values dialog box will open up.
6. Assign the parameter values for the test.
7. Click OK and test director will show up the manual runner. The step details dialog box will open up. Perform the execution process step by step.
8. After running all the steps return to the default manual runner display. End the test run by clicking on the end of run button. 

How to call tests with parameters in Test Director?

Testing an application is a complicated process. Test director has provided help in many tasks such as in the organization and management of the different phases of the testing process which is inclusive of various activities such as test planning, requirements analyzation, defects tracking and so on. 

Test director basically provides the tester with a frame work that is well organized for the testing of applications just before their deployment. Test plans typically evolve around the requirements that are new or have been modified therefore; there is a need of having a central data repository for the management and organization of the testing activities. 

Test director proves to be an effective guide while you go through the following tasks:

1. Requirements specification
2. Test planning
3. Test execution
4. Defect tracking etc.

The above mentioned 4 tasks also represent the 4 major phases of the test director testing process. In the phase of test planning you have the following tasks:

1. Defining the testing strategy
2. Defining test subjects
3. Defining tests
4. Creation of the requirements coverage
5. Designing the test steps
6. Automation of the tests
7. Analyzation of the test plan

A test plan tree is constructed and then the tests are executed for locating the defects and assessing the quality. The following tasks are involved:

1. Creation of the test sets
2. Scheduling the runs
3. Running the tests
4. Analyzation of the test results

How to call tests with parameters in test Director?

- When the test steps are designed, you have an option whether or not include a call to a manual test. 

- When the test is executed, this manual test is called as a part of the execution sequence. 

- The test that is called is actually a template test which has the characteristic that it can be reused as a test that is called by other tests. 

- It is possible to pass parameters to a template test. 

- Parameter is a variable for replacing a fixed value. 

- The values of the parameters can be changed by passing the desired value to the test that calls it. 

Example:

- Suppose there is a test in which you need to log-in with a specific user id and password. 

- There might be two users to the same test i.e., administrator and public. 

- For achieving this, two parameters are created to the test namely user id and password. 

- The value of these two parameters then can be modified according to whether log-in has to be public or administrative.

Follow the steps below to call a test with parameters:

1. Firstly, the design steps tab needs to be displayed for the test therefore click on the design steps tab.
2. Select the test with parameters that are required to be called by clicking on the ‘call to test’ button. A ‘select a test’ dialog box will open up.  Type in the name of the test to be found and click find button. Test director will highlight that particular test. Click OK.
3. Again you will get a ‘parameters of test …’ dialog box which will display all the parameters associated with that particular test.
4. Modify the parameter values in the value column according to your requirements. Values to the parameters can be assigned whenever a test is created to call the tests or whenever a test is added to the test set or whenever the test is run.  Click OK. The selected step will be added to the design steps.
5. Re-order the steps
6. Adjust the step size.

How to develop a test plan tree in Test Director?

Testing a software system or application is not a child’s play rather it requires whole lot of focus, organization, management and vigor. Testing phases or tasks such as specification of the testing requirements, planning and execution of the tests, tracking of the defects are made quite easy with the test director. 

In this article we shall discuss about how the test plan trees can be developed using the test director. After the all of the testing requirements have been defined, the testing goals need to be determined by carrying out various activities such as:

1. Examining the testing as well as the system environment.
2. Examining the software system or application under test (SUT and AUT).
3. Examining the testing process

- These three activities are particularly carried out so that the testing strategy designed to achieve the testing goals can be outlined. 

- After testing goals are determined, one proceeds to build a test plan tree. 

- The purpose of this test plan tree is to hierarchically divide the software system or application under testing in to smaller testing units or one can call them ‘subjects’.

- For each subject or unit in the test plan tree some tests are defined consisting of steps. 

- Next, the actions to be performed on the application as well as the expected results are defined for each of those steps. 

- Addition of parameters to the test step adds to its flexibility. 

Now how to keep track of the relationships shared by the testing requirements and tests? 

- Just add links between the two corresponding things.

- Other than being simple, another benefit of adding links is that you can be assured of the compliance with the requirements in all the stages of the testing process. 

- After getting done with this, you decide which all tests you want to get automated. 

- If you see the application as a whole unit to be tested it seems like a very big thing. 

- Here, in the test director, the application is divided into smaller units based up on its functionality with the help of the test plan module. 

- Test plan tree serves all this purpose and is referred to as the graphical representation of the test plan.

- Here the tests are displayed on the basis of the hierarchical relationship in their functions. 

- After all the subjects in the test plan tree have been defined the next step involves creating step for each and adding them to the tree.

- The below mentioned are the steps to be followed:

1. Open and log on the project for which the testing process is going on.
2. Make sure that the test plan module is on display and if it is not click on the test plan module to do so.
3. Now you need to add a subject folder to the test plan tree by clicking on the new folder button. Give a name and description for the folder and hit OK button. You will see a new subject folder under the main subject folder in the test plan tree.
4. Next step is to add a test to the folder we created above by clicking on the new test button. Give a name for test and click OK. You will require to fill in the following details like level, review status and priority. This test then will be added to the test plan tree.
5. Go to the details tab and you can fill up the following details:

a)   Test name

b)   Test designer

c)   Creation date

d)   Test status etc.

e)   description

How to design and copy test cases in test director?

Application testing process is not the one that can be completed in a jiffy. It demands constant input in form of efforts, organization and maintenance. Well, all this becomes easy when you are assisted by mercury interactive’s test management tool.
Test director saves you a great deal of efforts for tasks such as requirements analysis, test planning, test execution, defect tracking etc. here in this article we are going to tell you how you can design as well as copy the test cases in test director. After the tests created for all the subjects have been added to the test plan tree and the basic test information has been defined, the test cases or the test steps are defined.
By defining them we mean that more details or step by step instructions are provided for how that particular test case is to be executed. Each step of a test case consists of two things namely:
1. Actions to be performed on the application under testing or AUT and
2. The expected results.

Test steps can be created either for manual tests or automated tests using test director. For manual testing it is said to be complete when you are done with the designing of the tests.
Then, the test execution can be straightaway be started by using the test plan tree. But in the case of the automated testing, an addition step is to create automated test scripts using any other mercury interactive tool such as Winrunner or some other third party tool.

Steps for designing test cases

Below mentioned are the steps that one can follow for designing a test case:
1. It has to be made sure that the test plan module is on display and if it is not click on the test plan tab to turn it on.
2. The test case for which you are about to design the test steps also needs to be displayed. You can do this by simply clicking on the name of that particular test.
3. Next you need to launch the design step editor by clicking on the ‘design steps lab’.
4. In the design step editor dialog box clicking on the new step button you will get a new step dialog box which will ask you enter a step name which is by default a sequential number.
5. Now for defining that step you require to fill up the following fields and click OK:
         a) Step name
         b) Description
         c) Expected result
6. Last step is to click OK which will close the design step editor and display the design steps.

How to copy the test cases?

In test director you get the option of copying the test cases either from the same project or from some other. Follow the below mentioned steps:
1. You need to turn on the design steps tab and select that particular test case from the test plan tree which you want to be copied.
2. Next step involves selecting the steps of the test cases which you want to be copied. You will observe a gray sidebar, position the mouse pointer there and you will see that the pointer changes to  ->. Now hold down the shift and select the steps you want to be copied.
3. By using the copy steps copy down all the selected steps.
4. Next paste the steps where you want them to be copied in the test plan tree by using the paste steps button in the design steps tab.

How do you modify and convert requirements in Test Director?

There is no doubt in the fact that one kicks off a testing process by inputting the specification of the requirements employing the requirements module of the test director. Requirements are a necessity in the testing process. Also, the foundation on which a testing team carries out the testing process is laid down by the requirements itself. The definition of the requirements is represented in the form of what is called a requirements tree. This is actually a graphical representation of the requirements as stated in the document view with the only difference being of hierarchical display. 

The requirements can be grouped as well as sorted out in a requirements tree. The following tasks can also be carried out:

1. Task allocation monitoring.
2. Monitoring the progress of the requirements.
3. Generation of the detailed graphs and reports.

Once the tests have been created in the test plan module they have to be linked to the corresponding requirements. 

Here in this article, we talk about the modification and conversion of the requirements in the test director. 

One can modify the requirements by following the below mentioned step sequence:

1. First, make sure that the requirements module is available on display. If in case it is not you need to open it using the requirements tab. Both the requirements tree as well as the document view will be displayed.
2. Your next step is to copy that particular requirement to which you want to make modifications from the requirements tree by clicking on the copy option. Next clicking on the paste option and you will get a warning saying that you are duplicating the requirement. Click OK and the requirement will be pasted in the same hierarchy level as that of the original requirement. Suffix _copy_ is added to the name of the requirement.
3. Next step, is to rename the requirement by following the usual procedure for renaming an object.
4. Next, move this requirement to a different location but in the same requirements tree. But the requirements should be pasted as child requirement. Click OK for confirmation and drag the requirement to any location you want in the requirements tree.
5. For deleting this requirement as well its child requirement use the delete option.

Once all the requirements have been created and defined, they can be used as a basis for providing definition of the test plan tree module. The conversion to test wizards can be used to get assistance for designing the test plan tree. Using this wizard you can convert the selected requirements from the requirement tree in to subjects or tests for the test plan tree.

Steps for conversion of Requirements

Now the below mentioned steps can be followed for the conversion of the requirements:

1. For the modification procedure make sure that the requirements is up for display and if it is not there do so by clicking on the requirements tab.
2. From the various requirements in the requirements tree select the one which you want to be converted.
3. Now launch the convert to tests wizard from the tool menu and from that click on ‘convert selected’ option.
4. You can go for the automatic conversion method by taking second option i.e., ‘convert lowest child requirements to tests’ for the conversion of the selected requirements in to tests.
5. Now clicking on the next button will start the conversion process and after the conversion the results will be displayed in the step 2 dialog box. 

How do you define and view requirements in Test Director?

Test director is currently available as a plug in or add – on as a support for HP quality center and works like a test management tool. The earlier versions of the test director i.e., version 6 and below worked as stand-alone desk top applications.

However, the next version i.e., the test director 7 was a standalone web application and was known to work on any of the browsers that happened to be supporting active technology. For all the testers world wide it has been easy to integrate with the other mercury interactive tools via test director.

Three facts regarding test director:

1. This tool is not going to work out for the collection of the requirements of a software system or application.
2. It is not an automated testing tool.
3. It cannot be integrated with the products save mercury interactive products.

Test director comes with four specific modules namely:

1. Requirements module
2. Test plan module
3. Test lab module and
4. Defects module

How can we define and view requirements in the test director?

- This is done using the requirements module. 

- In every test management process, specification of the requirements is the first important step. 

- It involves analyzation of the software system or application under test and determination of the requirements of testing that application.

- Requirements analysis somewhat helps in carrying out the coverage analysis. - The following tasks are involved:

1. Addition of new requirements or editing of the previously added ones.
2. Addition and editing of the child requirements.
3. Linking of the requirements to the associated defects.
4. Analyzation of the coverage.

- The requirements analyzation phase follows through the below mentioned steps:

1. Defining the scope: The scope of the requirements includes test goals and objectives and can be determined using the requirements documentation.
2. Creation of the requirements: A requirements tree needs to be built so that all of the testing requirements can be defined.
3. Providing details for the requirements: Detailing involves adding attachments, assigning priority levels to all the requirements if required for testing.
4. Analyzation of the requirements: This phase involves generation of the reports consisting of the graphs to provide an assistance in the analyzation of the testing requirements.

Steps for Defining Requirements

Follow the below mentioned steps for defining the requirements:

1. Launch the test director demo project. You will require to log on to the project if in case the project is not open.
2. Now clicking on the requirements tab will display the requirements module or the requirements tree.
3. One thing that you need to be sure of is that the document view of the requirements is also displayed.
4. Click on the new requirement option which will open the new requirement dialog box. Fill in the details and hit OK.
5. Click new child requirement button for adding a requirement as a lower level of hierarchy.

Steps for Viewing Requirements

For viewing the requirements follow the below mentioned steps:

1. First step is making sure that the requirements module is displayed and if not click on the requirements and turn on the document view of the requirements tree.
2. You can zoom in as well as zoom out of the requirements tree using the zoom in and zoom out buttons.
3. In some cases you may require to view the numeration of requirements. 
4. To view numerations go to view menu and click on the numeration option. If you make any changes in the requirements the same is updated by the test director and numerations are renumbered. 

What is a Silk Test Test plan? What are the types of text lines in a test plan file?

A silk test plan consists of large amounts of data as well as information based on which are the details of the plan which in turn will be used in the organization and the development of the software system or application. 

It has three basic qualities as mentioned below:

1. Well structured
2. Hierarchical
3. Ideal model

A silk test test plan constitutes of two parts which are entirely different:

1. First part consists of an outline which gives a detailed description of the all the requirements of the testing process.
2. Second part consists of a statement which establishes a relationship between the outline of the first part and 4test scripts as well as test cases which are bound to implement the requirements defined above.

What is a Silk Test Plan?

- Test plan helps in achieving a guided way for the creation as well as execution of the test cases. 

- A new test plan can be created by following the below mentioned steps:

1. Go to the file menu and then click on new option.
2. From the drop down list that follows select test plan and hit OK. You will get a test plan window. Fill in the required fields and click OK.

- This is a known fact that silk test specializes in the field of functionality as well as regression testing and has been a known product when it comes to web, java or windows based applications. 

- Silk test provides you with two ways for defining or creating the automated tests:

1. By using the record test case command for recording the actions and the verification of steps.
2. Using visual 4test scripting language by writing the test cases manually.

- Test plans in silk test are stored as ‘test plan (.pln)’ file type. 

- This file type is sometimes used for making combinations of the test scripts. 

- The basic purpose of a silk test test plan is to provide a frame work for the testing process and also for the organization and maintenance of the testing requirements. 

Benefits of using a Test Plan

Using a test plan has following benefits:

1. With test plan you have a chance to implement top down approach for defining the testing requirements, developing thoughts and refining the requirements.
2. Attributes can be assigned to individual tests or group of tests.
3. Redundancy is reduced single only actually implementing statements are allowed.
4. Can be used as a comprehensive inventory of requirements consisting of most general as well as specific requirements.

What kind of text lines are there in a test plan file?

Test plan file consists of 5 types of text lines that we have described below:

1. First type of text lines are the comments which are usually marked in green color.These types of text lines provide commentary type of information regarding the test code.
2. Group Description: This type of text lines are represented in bold black color. Furthermore, they are included so as to provide a description of a group of tests rather than describing individual tests. Usually, a test plan consists of many tests which are then grouped in to multiple levels of various groups.
3. Test Description: This type of text lines are written in blue color and are meant for showcasing the description of the individual tests only.
4. Test plan statement: This type of text lines in a test plan file provide information regarding the relations to the following elements:

a)   Test cases

b)   Link scripts

c)   Test data

d)   Closed sub test plans

e)   Include files to a test plan.

These are marked in red color.

5. Open sub plan file marker: These text lines are marked in magenta color and thus providing info regarding relations to link sub test plans with the master plan.