Subscribe by Email

Friday, November 30, 2012

What is a follow up alert? How to create follow up alerts in test director?

Test director is mercury interactive’s test management tool. 
- It helps in creating a quality assurance personnel plan and organizing the whole testing process usually termed as the test director testing process.
- It lets you build a data base consisting of the manual as well as automated test cases, test cycles, run tests, reports of the tracking defects and so on. 
- The test director instructs to create alerts automatically and notify the responsible people whenever some changes are encountered by the project. 
Alerts are generated for the changes that affect the project in one or more than one ways. 
- For generating automatic alerts, the administrator can activate the trace-ability notification rules based on the associations made among the requirements, defects and test.

What is a Follow Up Alert?

- Test director allows to add own follow up flag to a defect, test instance or a specific test so as  to remind oneself to follow up on an issue. 
- When the date of actual follow up arrives, an e – mail is send to the person’s mail box. 
- Test director notifies the tester by adding a trace that changes the flag to the changed entity or by mailing a notification whenever a change is made to the requirement, defect or test in the project. 
- Creating follow-up alerts is always useful since you are always reminded whenever it is required to follow up on some issues. 

Requirements for Follow up Alert

- Test director 8.0 should be installed on your system. 
- You must have access to all the four modules of the test director namely requirements, test plan, test lab and defects. 
- You must have either a sample project or an actual project on which you carry out the exercise.
- Work with a new copy of the project. 
- You should also have either a sample application or an actual application.  

Now we shall discuss the procedure to add a follow up flag to a defect whose status requires to be checked. 
When the follow up date comes, the flag icon is turned to red color and the test director sends a notification via e – mail. One thing that you should always take care of is that the flags have a specific user name which means only the user whose name is on the flag will be able to see it. 

Steps to create a Follow-up Alert

Follow the steps mentioned below to create a follow up alert:
  1. Click on the defects tab so as to turn on the defects module.
  2. From the defects grid select the defect for which you want to set up a flag to follow  up.
  3. Now for creating a follow up alert click on the ‘flag for follow up’ button and a flag for follow up dialog box will open up. Fill in the following details:
a)   Follow up by: select the date.
b)   Description: type:
Once done with filling up the details click ok. A flag icon will be added to the      defect record by the test director.
  1. To display the information bar for your follow up alert, double click with the follow up flag on the defect. A defect details dialog box will pop up and will display a yellow information bar with the follow up alert.
  2. To close the dialog box click on cancel button.

Thursday, November 29, 2012

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.
  1. To view all the attachments click on the attachments button in the left menu and you will see the list of URL attachments.
  2. 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.
  3. 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. 

Wednesday, November 28, 2012

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.
  1. Clear the history.
  2. You can add the report as a favorite view by clicking on the add to favorites button.
  3. Close the report. 

Tuesday, November 27, 2012

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

The graphs that are created during the test director testing process let you keep a track of the progress of the test plan, test runs, defect tracking, requirements and so on. Such graphs can be generated at any point of time during the process and also from any of the test director modules. The graphs created by the test director are based up on the default setting however they can be customized by the user.
A project consists of data of different types. The graphs that you create using the test director can help you a big deal in analyzing the relationships between these different types of data. Each of the modules of the test director comes with a number of graph generating options. After you are done with generating the graph, you can customize its various properties so it comes out exactly as per your specifications and displays the information you want and in the way you want. 

Now we shall mention the steps following which you can generate a defects graph which will show the summary of the defects by status as well as priority levels. 

Steps for generating Defects Graph

Follow the steps:
  1. Click on the defects tab to turn on the defects module of the test director. The defects module will be displayed in the defects grid.
  2. Now for choosing a graph go to analysis menu, then graphs, then summary, then group by status option. This will open up a defects summary graph. This graph is grouped by status by default.
  3. Next you need to clear the default filter. Clicking on the filter button will do the task for you. The filter dialog box will open up. You will see that the detected by field is set to the current user name by default. Here, click the clear button and the applied filter will be removed by the test director.
  4. If you want to define a filter for viewing the defects with high to urgent priority then click the filter condition box for the priority field in the filter dialog box. Clicking on the browse button will open up the select filter condition dialog box’. Then select the required logical expression in the right pane and in the left pan select the level. Click OK to save the settings and close this dialog box.
  5. Next for defining a filter for viewing the defects that are not closed click the filter condition box for the status field. Again open the select filter condition dialog box by clicking on the browse button. Select the ‘not’ logical expression and select closed in the left pane. Click OK to close this box and once again click OK to close the filter dialog box.
  6. For setting the X axis of the graph select priority on the right side of the window for viewing the number of defects according to priority.
  7. Clicking on the refresh button will refresh the graph i.e., a new graph will be displayed.
  8. For displaying additional defect details click on a bar segment of the graph. A drill down results dialog box will display the defects related to that bar segment. Close this dialog box by clicking on the close button.
  9. There are various graph views available such as the data grid view and pie chart. Clicking on the corresponding options will display the graph as a pie chart, grid and so on.
  10. Close the graph and click on the back button to go back to the defects module. 

Monday, November 26, 2012

How to add and match defects in Test Director?

Location of the defects and their effective repair forms an inseparable part of the application development and indeed of the test director testing process. Defects can be submitted by almost everyone involved with the development process such as the developers, end users and of course testers. The test director eases all the testing processes and thus defects can be submitted through it and can be tracked until they are appropriately repaired. 

In this article we shall discuss the following two things:
  1. Adding defects in the test director and
  2. Matching defects in test director

Steps in adding defects in Test Director

Whenever a defect is submitted to the test director it is processed through the following  four stages:
  1. New
  2. Open
  3. Fixed
  4. Closed
Addition of the defects to the test director can be carried out at almost any stage of the test process. Below we state the steps that you need to follow in order to add the defects in test director:
  1. Open the test director project with which you are concerned and log on to it.
  2. Next step involves displaying the defects module by clicking on the defects tab. The defect data will be displayed by the defects grid in a grid where each row is a representation of an individual defect record.
  3. Clicking on the add defect button will open up the ‘add defect’ dialog box. The fields displayed in red color are mandatory to be filled up.
  4. Fourth step involves describing the defect by providing the following details:
a) Summary: i.e., what problem the defect actually caused.
b) Category
c)  Severity
d) Subject
e) Detected in version
f) Description:
It includes the part of the code where the defect was discovered and 
what problem was actually encountered.
  1. Now you need to attach the URL address for the page where the defect was found by clicking on the Attach URL button. Clicking on that button will open up a attach URL dialog box. There type the address of the page and click OK. This URL will be displayed above the description box by the test director.
  2. Next run a spell check for the text in the description box. If any errors are found follow the replacement suggestions.
  3. Click on the submit button to submit the defect to the test director project.
  4. Finally, close the add defect dialog box by clicking on the close button. The defect will be added to the defect grid.

How to match defects in Test Director

- The purpose of matching the defects is to find similar defects so that the duplicate ones can be eliminated from the project. 
-  Every time a new defect is added the list of keywords is stored by the test director from the description and summary fields. 
-  The stored keywords are then used for matching the defects. 
- Articles, coordinate conjunctions, wildcards and Boolean operators are ignored by the test director while matching the two tests. 
- Below mentioned steps are for matching defects in test director:
  1. Like for adding the defects this also requires displaying the defects module. Do this by clicking on the defects tab.
  2. From the defects grid select the one you want to match. If in case you cannot find the required test search it using the clear filter/ sort button.
  3. Now click on the find similar defects button to find similar defects. The results will be displayed in the similar defects dialog box by the test director.The defects are searched based up on percentage of the similarity detected.
  4. Finally, click on the close button to close the similar defects dialog box. 

Sunday, November 25, 2012

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. 

Saturday, November 24, 2012

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.
  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Further, if required, some execution condition can also be added to the tests.
  6. 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. 

Friday, November 23, 2012

How to run a test automatically in Test Director?

The whole testing process revolves around the execution of the tests. As the changes are introduced in to the software system or application, running tests either manually or automatically becomes mandatory so that the defects can be located and quality can be assessed. 

How are tests run?

- One starts the testing process with the creation of the tests and adding these tests to a test set. 
- Tests are grouped into test sets by the test director so that some specific goals can be achieved. 
- Execution process of the tests can be controlled via the various controls provided by the test director. 
- Along with these controls, there are certain conditions and settings which need to be configured for the execution of the tests as desired by the tester. 
- The date and time can also be scheduled when the tests will be executed. 
Once the tests have been defined the tester can begin with the execution of the tests. 
- Whenever the tests are executed manually, it is basically the test steps that were defined earlier during the test planning which are executed one by one. 
The steps are passed or failed by the tester depending up on whether there is a match between the expected results and the actual results. 
- For the automatic run of a test, the selected tool is directly opened by the test director and the test is run. 
- The result hence obtained is exported to the test director. 
- Setting conditions and specifying date and time for the execution of a test both can be done with the help of the execution flow tab.
- In the execution, one thing should be noticed which is that the condition is always dependent on the result of some other specified test in the same flow. 
Also, the sequence in which the tests are to be executed can be specified. 

In this article we shall see how the test execution can be automated. The tool selected for the execution of the tests is opened directly by the test director and the tests are run on either local or remote machine. It is either choice if you want to run all the tests or some specified ones. 

For running the tests automatically one of the following tools must be installed on the system:
a)   Astra quick test
b)   Quick test professional
c)   Winrunnner

Follow the below mentioned steps:
  1. Clicking on the test lab tab will display the test lab module. This is a must for the automation of the tests.
  2. The test set you want to execute automatically should be displayed in the execution grid. For doing this click on the execution grid tab and select the required test from the test sets tree.
  3. Select a test. For running the winrunner test select the required test or if you want to run an astra quick test or QTP test select the required one. Next clicking on the run button will open up the execution dialog box and the test will be displayed.
  4. Configure the test run settings and select the ‘run all tests locally’ option for running the tests on the local machine.
  5. For running the tests click on run tests and the tool will be opened automatically by the test director and the tests will be run. The execution progress can be viewed in the status column.
  6. Once the execution of the test is complete close the execution dialog box by clicking on the exit option.
  7. Also the summary of the test results can be viewed in the execution grid.

Thursday, November 22, 2012

How to track defects in Test Director?

A software system or application cannot be considered productive and useful if it is full of defects. Hence, it becomes quite essential that all the defects present in the software system or application are located and repaired appropriately during the development process.
The end users, testers and developers can submit the defects that are detected during all the phases of the testing process. The test director helps incredibly in the submission of the defects detected in the software and tracking of them till they are well repaired. 

Life-cycle of a Defect

- Whenever a defect is submitted to the test director project, there are certain stages through which the defects are tracked namely:
  1. New
  2. Open
  3. Fixed
  4. Closed
- Once a defect is fixed, the tester can either reject it or reopen it. 
- At the initial stage of reporting the defect to the test director, the status that is assigned to the defect is ‘new’ by default. 
- The defect is reviewed by either a quality assurance or a project manager and it is determined whether or not the defect is to be considered for repair. 
- If the defect is not considered for repair i.e., if it is rejected the status ‘rejected’ is assigned to it. 
- If the opposite case is there i.e., if the defect is accepted for repair it is assigned a repair priority by the project manager or quality assurance and the status ‘open’ is assigned to it. 
- This defect is now assigned to one of the members of the development team for repair. 
- The developer repairs the defect and then the status ‘fixed’ is assigned to it. 
- The software system or application is then retested, thus ensuring that there is no occurrence of the defect again. 
- Even if in case the defect recurs, it is again assigned a new status ‘reopened’ by the quality assurance or project manager. 
- But if the defect gets properly repaired the status ‘closed’ is assigned to it by any of the two managers. 
- The test director also provides the option of adding some new defects to an existing test director project. 
- All information and data regarding the defects found within a software system or application is handled by the defects module of the test director.
- The following are the defects that are undertaken by the defects module of the test director:
  1. Creation of the defects.
  2. Editing of the defects.
  3. Linking defects to each other.

Stages of Defect Tracking Process

The following stages are involved in the defects process:
  1. Adding of the defects
  2. Reviewing of the new defects
  3. Repairing open defects
  4. Testing of new build
  5. Analyzation of the defect data
- In the first stage of the defect tracking process, the new defects detected in the software system or application are reported. 
- In the next stage, the new defects are put through a review process and the defects to be fixed are determined. 
- In the third stage, the defects are corrected by the developers who have been assigned to do the task.
- In the fourth stage, the new build of the application is tested and this process is continued until and unless all the defects are repaired. 
- The last stage of the defect tracking process witnesses the generation of the reports so as to provide some assistance to the developers for the analyzation of the progress of repairing the defects. 
- Also, in this stage, the date of release of the software system or application is determined. 
- Later, it is determined whether to cancel the rejected defects or take action on them further. 
- The following productivity tools assist the process:
  2. Filters
  3. Sort
  4. Manage columns
  5. Favorites

What issues should be considered when deciding whether to automate a test? How to generate an automated test script?est Scripts, Scripts

Execution of the test sets lies at the center of any testing process. As the software system or application encounters changes, the defects are located by running both manual as well as automated tests in the project. Also, the quality of the tests is assessed by running the tests itself. 

Issues considered when deciding to go for automation?

- Deciding which all tests have to be automated is a part of the test planning process. 
- Two options namely manual and automated are available for the execution of the tests. 
- If you go with the manual execution of the tests, you can begin with the execution just after you finish defining the test steps. 
- If you go for automating the tests, the test scripts need to be generated and completed. 
- Below we state the issues that should be considered when deciding to go for automation:
  1. Do Automate: Only the tests which are data driven or which make use of multiple data values for the same operation, which run with every new version of the application as a measure to check its functionality i.e., regression testing, which are for stress testing i.e., run many times and tests that facilitate the checking of a server system or multi-user client system (load testing) must always be automated.
  2. Do not automate: The tests which are meant for a single execution, need to be executed immediately, check for the usability of the tests and whose result cannot be predicted should not be automated.

Steps for generating Automated Test Scripts

Below mentioned steps can be followed for the generation of the automated test scripts:
  1. First, click on the test plan tab in order to enable the display of the test plan module.
  2. Locate the manual test that you want to automate by selecting the subject folder available at the root of the test plan tree. There click on the find button and the find folder/ test dialog box will open up.
  3. Type the name of the test to be searched for in the ‘value to find’ field of the box. Check the ‘include tests’ check box so that the test director can be instructed to look for folders and tests. Finally click on find option. ‘Search results’ dialog box will pop up thus displaying all the possible matches. Click on go to button and the test will be highlighted in the test plan tree. Close this dialog box.
  4. Click on the design steps tab in order to display the design steps tab.
  5. For generating a test script click on the generate script button. You can choose either of the following options:
a) QUICKTEST_ TEST: For generating an astra quicktest test or quick test professional test.
b)   WR – AUTOMATED: For generating a winrunner test.
The above two options will be available if the corresponding add ins have been installed. Once the test has been automated, the manual test symbol ‘M’ will be replaced by automated test icon.
  1. For viewing the test script click on the test script lab. Click on the launch button for displaying and modifying the test script in the testing tool where it was created.
Whenever an automated test is run, the testing tool selected by the tester is opened by the test director automatically and the test is run on either the remote hosts or local machines. The tests can be run either from the execution flow tab or the execution grid tab.

Wednesday, November 21, 2012

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. 

- 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.

Facebook activity