Interview Questions

WinRunner: Test Director - Set Up Recommendations:

Mercury WinRunner FAQ

(Continued from previous question...)

WinRunner: Test Director - Set Up Recommendations:

Before a tester starts creating folders and test scripts, they should configure their Test project using the Administration menu.
1. Create various Users and User Groups for your project through the Administration -> Setup Users… menu item. Test Director comes with the following Pre-defined users and groups. We recommend that you create a user id that is similar to your Network login. You also have the option to create a password or leave it blank. The default is blank. You can also create your own groups or use the default groups provided by Test Director.
Default Users and Groups:
. Admin
. Guest
. TDAdmin Has full privileges in a TestDirector project. This is the only type of user which can make changes to the information in the Setup Users dialog box. It is recommended to assign this user type to one person per group who will serve as the TestDirector Administrator.
. QATester Can create and modify tests in Plan Tests mode, and create test sets, run tests, delete test runs, and report defects in Run Tests mode. This user type is recommended for a quality assurance tester.
. Project Manager Can report new defects, delete defects, and modify a defect's status. This user type is recommended for a project manager or quality assurance manager.
. Developer Can report new defects, and change a defect's status to Fixed. This user type is recommended for a software developer.
. Viewer Has read-only privileges in a project.
2. Test Director also give you the option to customize your projects by creating user-defined fields for the dialog boxes and grids, creating categories and modifying drop down lists. These options enable you to add information that is relevant to your project. Modification to your projects are done using the Administration -> Customize Project Menu item. For more details on how to customize your project please see Chapter 3 in the Test Director's Administrators Guide.
3. Decide on Script Naming Convention and consistently use the naming convention for all tests created within the project. Please reference the Naming Conventions section for more information.
4. Create Test Folders to organize your tests into various sections. Examples of possible folder(s) names could be the types of testing you are doing ie: (functional, negative, integration ) or you could base your folder names on the specific modules or windows you are testing.

5. Create test scripts on the Plan tests folder using the New button in the test frame or menu item Plan -> New Test. The Test window has four tabs, Details, Design Steps, Test script and attach.
The Details tab, should be used to list all the information regarding the test. Test Director defaults to displaying the Status: Design; Created: date and time; Designer: your id.
. The Design Steps Tab, should be used to list detail instructions on how to execute your test.
. The Test Script tab, is used for tests that are turned into automated tests, on this page the automated WinRunner code will appear.
. The Attach Tab, can be used to attach bitmaps or other files required for testing to the script.
6. When creating folders, tests and test sets in Test Director make sure every item has a description.
7. Create a "Documentation" test to document how to set up your testing environment and run your tests.
8. It is recommended that you write your test scripts as detailed as possible and not assume that the executor of your test "knows how to use your module". By making your scripts as detailed as possible, this will allow others from outside your project to understand how to execute your tests, in the event that they have to run the tests.
9. Create Test Sets to group like test together, or to specify the order in which your tests should run. Test director has a limit of 99 test scripts per test set.
10. Export the test scripts into word via the Document Generator, Menu item Report -> Document Generator.

(Continued on next question...)

Other Interview Questions