1) How you used WinRunner in your project?
a) Yes, I have been using WinRunner for creating automated scripts for GUI, functional and regression testing of the AUT.

2) Explain WinRunner testing process?
a) WinRunner testing process involves six main stages
i. Create GUI Map File so that WinRunner can recognize the GUI objects in the application being tested
ii. Create test scripts by recording, programming, or a combination of both. While recording tests, insert checkpoints where you want to check the response of the application being tested.
iii. Debug Test: run tests in Debug mode to make sure they run smoothly
iv. Run Tests: run tests in Verify mode to test your application.
v. View Results: determines the success or failure of the tests.
vi. Report Defects: If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window.

3) What is contained in the GUI map?
a) WinRunner stores information it learns about a window or object in a GUI Map. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested. Each of these objects in the GUI Map file will be having a logical name and a physical description.
b) There are 2 types of GUI Map files.
i. Global GUI Map file: a single GUI Map file for the entire application
ii. GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.

4) How does WinRunner recognize objects on the application?
a) WinRunner uses the GUI Map file to recognize objects on the application. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested.

5) Have you created test scripts and what is contained in the test scripts?
a) Yes I have created test scripts. It contains the statement in Mercury Interactive’s Test Script Language (TSL). These statements appear as a test script in a test window. You can then enhance your recorded test script, either by typing in additional TSL functions and programming elements or by using WinRunner’s visual programming tool, the Function Generator.


- Shanthi

1) How does WinRunner evaluates test results?
a) Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window.

2) Have you performed debugging of the scripts?
a) Yes, I have performed debugging of scripts. We can debug the script by executing the script in the debug mode. We can also debug script using the Step, Step Into, Step out functionalities provided by the WinRunner.

3) How do you run your test scripts?
a) We run tests in Verify mode to test your application. Each time WinRunner encounters a checkpoint in the test script, it compares the current data of the application being tested to the expected data captured earlier. If any mismatches are found, WinRunner captures them as actual results.

4) How do you analyze results and report the defects?
a) Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window. If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window. This information is sent via e-mail to the quality assurance manager, who tracks the defect until it is fixed.

5) What is the use of Test Director software?
a) TestDirector is Mercury Interactive’s software test management tool. It helps quality assurance personnel plan and organize the testing process. With TestDirector you can create a database of manual and automated tests, build test cycles, run tests, and report and track defects. You can also create reports and graphs to help review the progress of planning tests, running tests, and tracking defects before a software release.


-Shanthi

Hi,

How you integrated your automated scripts from TestDirector?.


Sabita

When you work with WinRunner, you can choose to save your tests directly to your TestDirector database or while creating a test case in the TestDirector we can specify whether the script in automated or manual. And if it is automated script then TestDirector will build a skeleton for the script that can be later modified into one which could be used to test the AUT.


-Shanthi

What is the disadvantage of loading the GUI maps through start up scripts?


-Shanthi

Hi,

If we are using a single GUI Map file for the entire AUT then the memory used by the GUI Map may be much high. If there is any change in the object being learned then WinRunner will not be able to recognize the object, as it is not in the GUI Map file loaded in the memory. So we will have to learn the object again and update the GUI File and reload it.

Sabita

Hi All,

Anyone have the experience in migrating WinRunner TSL Scripts into QTP VB Scripts, either using any third party tool, not calling the TSL scripts in QTP. If you then let me know.




-Shanthi

Hi,

There is tool called QTP Genei which converts winrunner scripts to QTP scripts. Sierra Atlantic, Hyderabad has developed that tool.

Sabita

Hi frds,

In GUI Testing, i have used GUI checkpoints to check the
properties. In future reference if i need to view the actual screen of
GUI properties that has failed.Where will i find it?

Waiting for the reply...

-Shanthi

Hi,

All these values are stored in EXP folder.


Sabita

Hi All,

There is table in an application whose location keeps changing.To
overcome this i used regular expression.The following is the statement that used to regularize:

NewWebTable= "{ class: \"object\", MSW_class: \"html_table\ ",
location: \"![0-9][0-9] \"}";

But it displays a syntax error.


Could any of you point the error in this statement & let me know
the correct one.

Thank you

Hi Shanthi

In descriptive scripting u should use quotes - "";
Try without using the ""
for eg:
NewWebTable= "{ class: object, MSW_class:html_ table, location:[0- 9]
[0-9]}";
Just try this and let me know.

-Sabita

Thanks sabita, will try out and let know the result.

What is the command in Winrunner to invoke IE Browser?



-Sabita

Sabi,

Use this command,

web_browser_invoke(IE,URL);


-Shanthi

Framework of winrunner?

Depending on the Project what Architecture we had Designed (Test Automation Architecture For Winrunner) for the project. We will place all the folders in our centralized repository like this COMPANYNAME_PROJECTNAME_AUTOMATION this is the main folder and the sub folders are Ex: Test Data,GUI


-Shanthi

Shanthi,

Let me know what is the use of framework in WR?



-Sabita

It is the Template test provides a basic framework of an automated test that navigates through your application. It opens and closes each window, leaving space for you to add code (through recording or programming) that checks the window WinRunner, Mercury Interactive and the Mercury Interactive.


-Shanthi

Difference between set_window and window_activate:

set_window function is used for giving input to the window.

win_activate function is used for the activate window.Note: In scripts, important to use win_activate function before set_window function in point of syncronization

-Shanthi

1. WinRunner testing process involves six main stages

• Create GUI Map File so that WinRunner can recognize the GUI objects in the application being tested
• Create test scripts by recording, programming, or a combination of both. While recording tests, insert checkpoints where you want to check the response of the application being tested.
• Debug Test: run tests in Debug mode to make sure they run smoothly
• Run Tests: run tests in Verify mode to test your application.
• View Results: determines the success or failure of the tests.
• Report Defects: If a test run fails due to a defect in the application being tested, you can report information about the defect directly from the Test Results window.

2. What is Contained in the GUI Map ?
WinRunner stores information it learns about a window or object in a GUI Map. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested. Each of these objects in the GUI Map file will be having a logical name and a physical description.
There are 2 types of GUI Map files.
• Global GUI Map file: a single GUI Map file for the entire application
• GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.

3. How Does WinRunner recognize objects on the Application?
WinRunner uses the GUI Map file to recognize objects on the application. When WinRunner runs a test, it uses the GUI map to locate objects. It reads an object’s description in the GUI map and then looks for an object with the same properties in the application being tested.

4. How Does WinRunner evaluates test Results?

Following each test run, WinRunner displays the results in a report. The report details all the major events that occurred during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, you can view the expected results and the actual results from the Test Results window.

5. Have You Created test Scripts and what is contained in the Test Scripts?

Yes I have created test scripts. It contains the statement in Mercury Interactive Test Script Language (TSL). These statements appear as a test script in a test window. You can then enhance your recorded test script, either by typing in additional TSL functions and programming elements or by using Win Runner’s visual programming tool, the Function Generator.

-Shanthi