Explain about the Paged Memory and Segmentation techniques?

Paging and segmentation, both are memory management techniques. 

What is Paging?

- This technique has been designed so that the system can store or retrieve data from the virtual memory or secondary memory of the system to be loaded in the main memory and used. 

- In this scheme, the data from the secondary memory is retrieved by the operating system in blocks of same size commonly known as the paging. 

- This is why the technique has been called the paging memory – management scheme. 

- This memory management scheme has a major advantage over the segmentation scheme. 

- The advantage is that non-contiguous address spaces are allowed. 

- In segmentation, non-contiguous physical address spaces are not allowed. 

- Before the paging actually came in to use, the whole program had to be fitted in to the contiguous memory space by the systems. 

- This in turn led to a number of issues related to fragmentation and storage. 

- Paging is very important for the implementation of the virtual memory in many of the operating systems that are general purpose. 

- With the help of paging memory management technique, the data that cannot be fitted in to the physical memory i.e., RAM can be easily used. 

- Paging actually comes in to play whenever a program makes an attempt for accessing the pages that have not been presently mapped to the main memory (RAM). 

- Such situation is termed as the page fault. 

- At this point the control is handed over to the operating system for handling the page fault.

- This is done in a way that it is not visible to the interrupt raising program. 

The operating system has to carry out the following instructions:

1. Determining the location of the requested data from the auxiliary storage.
2. Obtaining a page frame in the main memory that is empty to be used for storing the requested data.
3. Loading the data requested in to the empty page obtained above.
4. Making updates to the page table so that new data is only available.
5. Returning the control interrupting program and retrying to execute the same instruction that caused the fault.

What is Segmentation?

- This memory management technique involves dividing the main memory in to various sections or segments.

- In the system that makes use of this management technique, a value identifying the segment and its offset is contained in the reference to that memory location. 

- Object files that are produced during the compilation of the programs make use of the segments when they have to be linked together to form an image of the program and this image has to be loaded in to the memory.  

- For different program modules, different segments might be created. 

- Some programs may even share some of the segments.

- In one way, memory protection is implemented by means of memory segmentation only.

- Paging and segmentation can be combined together for memory protection. 

- The size of memory segment is not always fixed and can be as small as a byte. 

- Natural divisions such as the data tables or the individual routines are represented by the segments.

- This is to make the segmentation visible to the programmer. 

- With every segment, a set of permissions and length is associated. 

- A segment can be referred to by the process only in a way that is permitted by this set of permissions. 

- If this is not done, a segmentation fault is raised by the operating system. 

- Segments also consist of a flag that indicates the presence of the segment in the main memory of the system. 

Explain Tellurium - Web Functional/Regression Test Tool

- Tellurium is an automated testing framework developed exclusively for the web–based applications.

- It is an open source tool and based up on user interface module.

- All UI elements grouped together are called as the UI module. 

- Usually, a composite UI object is what that a UI module represents in a format similar to that of the basic nested UI elements. 

- Building of UI locators is actually possible because of the UI module. 

- This tool comes with a Firefox plug – in called the TrUMP (tellurium UI model plugin) using which one can create UI modules automatically.

- The duty of the framework is to perform object to locator mapping or OLM. 

- It does this at the execution time automatically so that the user finds it easy to define the UI objects just by their respective attributes. 

- Another technique used by tellurium is the GLC or the group locating concept for the exploitation of the information contained in the UI components. 

- This information is used for locating the locators.

- It defines a complete new language for web testing known as the domain specific language or DSL. 

- UI templates are one of the powerful features of tellurium. 

- These templates can be used for representing many identical UI elements with their dynamic size at the run time. 

- These elements are quite useful for testing dynamic web elements like for example a data grid.

- Another characteristic feature of tellurium is that it can composite the UI objects very nicely in to tellurium widget objects. 

- The tellurium widgets thus obtained can be packed as a jar file. 

- Each of these widgets can be used as a single tellurium UI object once included with the jar file. Java and groovy wrote the code for the tellurium core. 

- However, tellurium trump and engine can be implemented with jQuery and JavaScript. 

- Users are free to test cases in any of these languages: groovy, pure DSL, or java. 

- Tellurium is kind of a portable framework and runs up on selenium. 

- JUnit and TestNG testing frameworks are both supported by tellurium. 

- Tellurium is hosted on Google code as an open source project.

- It comes with Apache license 2. 

- The credit for the creation of this tool goes to Jian Fang of the Georgia institute of technology.

- The major flagship project of the tellurium team is the tellurium core. 

- The UI modules act as a backbone to the tellurium tests since they define the html content of the page that is being tested. 

- But it does not make use of CSS and xpaths for defining the UI elements as selenium do. 

- It uses a much better thing i.e., DSL that also defines the relationships among those modules. 

- JUnit or TestNG can be used as testing container as preferred by you. 

- It is required to write the UI module DSL for writing a selenium test case. 

- This can be either be done using TrUMP or manually. 

- The robustness of the tests are further improved by the tellurium’s santa algorithm. 

- This algorithm locates the UI module at the execution time DOM. 

- But this feature is only available in 0.7.0 and higher versions.

- The lower versions require that the run – time locators are generated by the tellurium core based up on the definition of the UI module. 

- The selenium commands are then passed by to the tellurium for locating individual UI elements. 

- Using trump UI module DSL can be generated just by clicking on the page elements. 

- The DSL then can be saved to a groovy class and can be used by the tests any time. 

- It is the use of UI modules that have made the tellurium so expressive.

What is trace-ability alert? How to trigger a trace-ability alert in Test Director?

The process of sending e–mails in order to notify the ones that are responsible whenever some change is made to the project. This can be done by instructing the test director to create an alert whenever a change occurs and send e – mails appropriately. One’s own follow up alerts can also be added. 

There are certain rules called the trace-ability notification rules (based up on the associations that were made in the test director among the tests, requirements and defects) which are activated by the test director administrator for generating the automatic trace-ability alerts.

On what occasions a trace-ability alert issued?

Only for the following issues test director can generate the trace-ability alerts:

1. Whenever a requirement (except change of a status) changes, the designer of the associated tests is notified by the test director.
2. Whenever a requirement having an associated test changes, all the project users are notified by the test director.
3. Whenever the defect status changes to ‘fixed’, the responsible tester of the associated test is notified by the test director.
4. Whenever a test run is successful, the user assigned to the associated test is notified by the test director.

Steps to trigger trace-ability alert

1. Log on to the project  as a different user.
2. Click on the test plan tab to turn on the test plan module which will display the test plan tree. Expand the concerned subject folders and select the required test. A designer box displaying the user name in the details tab in the right pane is seen. One thing to be noted is that whenever an associated requirement changes, the trace-ability notification is only viewed by the designer.
3. Click on the requirements tab to turn on the requirements tree and also make sure that it is in the document view.
4. Among the requirements choose the one that you want to change.
5. For changing the priority of the requirement click on the priority down arrow and select the required priority. This will cause the test director to generate an alert for the test associated with the requirement selected above. Also, an e – mail will be sent to the designer who designed this test.
6. When you are done log out of the project by clicking on the log out button present on the right side of the window.

How to view a trace-ability alert?

This trace-ability change can be viewed for a single entity or all the entities in the project. Here by entity we mean a test, a defect or a test instance. To view the trace-ability alert follow the below mentioned steps:

1. Log on to the project as the designer of the test.
2. Click on the test plan tab to view the test plan tree. Expand the subject folders to display that test. You will see that the test has a trace changes flag which is an indication of the fact that a change was made to the requirement associated with it.
3. Clicking on the trace changes flag for the test will enable you to view the trace-ability alert. Also, the trace changes dialog box will open up. Clicking on the requirement link will make the test director to highlight that particular requirement in the requirements module.
4. For viewing all of the trace-ability alerts click on the trace all changes button in the common test director tool bar. A dialog box listing all the trace-ability changes will open up.
5. Once done close the dialog box. 

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.

4. 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.
5. To close the dialog box click on cancel button.

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 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 do you define Test Sets in Test Director? How do you add tests to a Test Set?

One can begin with the creation of test sets and choosing which all tests are required to be added to the test sets. 

What is a test set?

- A test set is a collection of tests in the test director’s terminology. 

- The concept of test set was developed so that specific testing goals could be achieved. 

- The execution of the tests in a test set can be controlled by scheduling the data and time for the execution and setting some testing conditions. 

- After the test sets have been defined, the time comes to execute them. 

- In the manual execution of the test sets the test steps defined earlier are executed. 

- The success or failure of test step depends on the one who is executing the tests based up on whether the expected and actual results match.

- In the automated execution of the tests, the selected testing tool is opened up by the test director, the test is run and the test results are exported to the test director. 

In this article we shall see how the test sets are defined and how tests are added to the test sets. 

- Once the tests have been designed in the test plan module, a test sets tree is created which makes it easy for the tester to organize the whole testing process by making groups of the test sets in a folder. 

- The test sets are organized at different hierarchical levels in the test lab module. 

- It is possible for the tester to include both the automated as well as manual tests in the test sets. 

- Also, there occurs no problem if at all the same tests are included in a number of test sets. 

- For the creation of an exact test set it is important that you keep your testing goals clear and concise from the beginning of the testing process itself. 

- Also the issues such as following need to be considered:

1. Current state of the application and
2. Addition of new features
3. Modification of new features.

Test director offers you some categories of test sets that can be created:

1. Sanity
2. Normal
3. Advanced
4. Regression
5. Function

Follow the steps:

1. Open the project.
2. Click on the test lab to display the test lab module.
3. Now you need to add a new folder to the test sets tree. Go in the left pane of the test sets tree and select the root folder. Create a new folder in it by specifying a name for it and click ok.
4. Now add the test set to the test sets list by clicking on the new test set button. In the new test set dialog box enter the name of the test set and its description.
5. Next you need to define the details of the test set by clicking on the test set properties and then details link. Select the status of the test set, it opening date and closing date.
6. In case there is an event failure you need to set the rules for automated tests in the test set.

How to add tests to a test set?

For adding the tests to a test set follow the below mentioned steps:

1. Display the test lab module by clicking on the test lab tab.
2. From the test sets tree select the test set to be added and then click execution grid tab.
3. Go to the select tests button and you can see the test plan tree. If any filters have been applied they need to be cleared using the set filter option.
4. Select the folder containing the tests that you want to add and then click ‘add tests to test set’ button. For confirmation click yes. Parameters of test dialog box will pop up since the tests that are being added contain unassigned parameters.
5. When you are done close the test plan tree by clicking on the close button.  

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. 

Explore Test Director Window, Test Director Modules and elements?

The test director is a web based application and it provides well support to communication of a very high level. Further, it regulates collaboration between the testing teams which are widely distributed. Overall, it helps in driving a global application testing in a more effective and efficient manner. 

Being the global test management tool, it is also counted in the list of the industries’ best test management solution.

Features of Test Director

Test director comes with a whole lot of features to make software testing a better experience:

1. Web based site administrator
2. Domain management
3. Collaboration module
4. Advanced reports add – in
5. Automatic trace-ability notification
6. Hierarchical test sets
7. Work flow for all modules of the test director
8. User industry standard repositories
9. Link test plan to requirements
10. Integrates with MS office
11. Manages automated and manual tests
12. Accelerates testing cycles
13. Supports test runs across boundaries
14. Integrates with third party and internal tools
15. Structured information sharing
16. Easy defect reporting
17. Customization reports
    

Here we shall about the following:
1. Test director window, 
2. Elements and 
3. Test director modules.

Test director helps in the following tasks:

1. Organizing and managing all the phases of testing.
2. Specifying the test requirements
3. Planning tests
4. Executing tests
5. Tracking the defects and so on.

- The test director launched from one’s web browser by requesting the url of the test director. 

- When you enter this URL and press enter the test director window pops up.

- If you are running the test director, it will take some time to get downloaded in your system. 

- Whenever the test director is launched a version check is automatically carried out and the latest version is downloaded. 

- Once done with this, you will get a test director log-in window. 

- Now you select a domain among the list of domains provided by the test director or you can select default. 

- In the project list go for testdirector _ demo. 

- You need to log-in as a QA tester. 

Test Director Modules

- In the test director window click on the requirements tab. 

- This requirements tab represents the requirements module which enables you to define the test specifications which includes the following things:

1. Defining purpose of testing
2. Defining requirement topics
3. Analyzation of the requirements

- Similarly, the test plan tab represents the test plan module which powers you to create a test plan based on the requirements specified above. This module facilitates the following tasks:

1. Defining goals and strategies
2. Dividing the plan into categories
3. Development of  the tests
4. Analyzation of the plan.

- With the test lab module the tests can be run on the software system or application and the result can be analyzed. The defects module you can carry out the following tasks:

1. Add the defects
2. Determination of the repair properties
3. Repair of the open defects
4. Analyzation of the data

Elements of Test Director

Now coming to the elements of the test director, there are some elements that are common to all the test director modules and these are:

1. Test director tool bar
2. Menu bar
3. Module tool bar
4. Tools button
5. Help button
6. Log out button

All of these elements can be found in the top level of the test director window. Module tool bar consists of the buttons for the commands that are frequently employed in the current module.