Software QA FYI - SQAFYI

Mercury WinRunner FAQ

Part:   1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  37  38  39  40   41  42  43  44  45 

WinRunner: Test Director - Documentation Standards:

. Use a consistent naming convention for all test scripts and tests.
. Put Detailed descriptions on all test folders and test scripts to explain the purpose of the tests.
. Each test script should have a detailed test step associated with it.
. Before any automation project is started, the tester should write an automation standards document. The automation standards document will describe the following:
. Automation Environment
. Installation requirements
. Client Machines Configurations
. Project Information
. WinRunner and Test Director Option Settings
. Identify Servers, Database and Sub System tests will run against
. Naming Convention for project
. Specific Recording Standards that apply to individual project.


WinRunner: Test Director - Naming Conventions:

. Never call a test "tests", WinRunner/TestDirector has problem distinguishing the name test with the directory tests.
. The project automation document will specify any naming conventions used for the individual projects.


WinRunner: Test Director - Importing WinRunner tests into Test Director

1. bring up Test Director
2. select Plan - > Import Automated Tests
3. select your tests and import them
4. select the test grid button
5. change each tests subject to point to the folder you want them in
6. now copy all the tests from un-attached to the folder.
7. close test director
8. bring up test director again.
9. If after all this they are not there, create a dummy test to refresh the tree view, the tree window does not seem to refresh very well.


WinRunner: Test Director - How to delete Mercury Toolbar out of MS Word

If you ever play with the Test Director import into word feature, you will automatically create a test director toolbar in your MS word application. They best way to get rid of this toolbar is to;
1. Shut down word if open
2. Bring up windows explorer
3. Navigate to C:\Program Files\Microsoft Office\Office\STARTUP
4. Delete all instances of Tdword.*
5. Restart word and verify it is now gone.


WinRunner: Other Test Director Features

The Test Director application has a number of other features:
1. Running Manual tests via Test Director application. Test Director has a feature that allows you to run your manual tests through the Mini Step Utility. This feature allows you compare the actual outcome to the expected results and record the results in the Test Director database at run time.
2. Test Director also has the capability of converting your manual tests into Automated Tests in the WinRunner application.
3. Test Director also provides reporting and graphing capabilities, that will assist you in your reviewing the process of test planning and test execution. Test Director provides a number of standard reports and graph formats as well as allows the user to create customized reports and graph.
4. Defect Tracking. Test Director also provides a Defect tracking tool in the Test Director product.


WinRunner: How to see the internal version of WebTest in your machine?

To see the internal version in your machine, right-click the ns_ext.dll file, select Properties, and click the Version tab. The ns_ext.dll file is located in the arch subdirectory of your WinRunner directory.


WinRunner: Web sites contain ActiveX controls

If your web sites contains ActiveX controls, you must install ActiveX add-in support when you install the WebTest add-in.

Part:   1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  37  38  39  40   41  42  43  44  45 

Mercury WinRunner FAQ