Q1. How did you use WinRunner in your project?
Ans: I have been using WinRunner for creating automated scripts for GUI, functional and regression testing for AUT.
Q2. Explain WinRunner testing process?
Ans: WinRunner testing process involves six main stages
1) Create GUI Map: Create File so that WinRunner can recognize the GUI objects in the application being tested.
2) Create test: Create test scripts by recording, programming, or a combination of both. While recording tests, insert checkpoints where we want to check the response of the application being tested.
3) Debug Test: Run tests in Debug mode to make sure they run smoothly
4) Run Tests: Run tests in verify mode to test the application
5) View Results: View Results determines the success or failure of the tests
6) Report Defects: If a test run fails due to a defect in the application being tested, we can report information about the defect directly from the Test Results window.
Q3. What is contained in the GUI map?
Ans: 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 phycical description. There are two types of GUI Map files.
1) Global GUI Map file: A single GUI Map file for the entire application.
2) GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.
Q4. How does WinRunner recognize objects on the application?
Ans: WinRunner uses 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.
Q5. Have you created test scripts and what is contained in the test script?
Ans: 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. We can enhance the recorded test script, either by typing in additional TSL functions and programming elements or by using WinRunner's visual programming tool, the Function Generator.
Q6. How does WinRunner evaluate test results?
Ans: Following each test run, WinRunner displays the results in a report. The report gives details of all the major events that occured during the run, such as checkpoints, error messages, system messages or user messages. If mismatches are detected at checkpoints during the test run, we can view the expected results and the actual results from the Test results window.
Q7. Have you performed debugging of the scripts?
Ans: Yes, I have performed debugging of the 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.
Q8. How do you run the test scripts?
Ans: We run tests in Verify mode to test the 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.
Q9.How do you analyze results and report the defects?
Ans: Following each test run, WinRunner displays the results in a report. The report details all the major events that occured during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, we can view the expected results and the actual results from the TestResults 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.
Q10. What is the use of Test Director Software?
Ans: Test Director is Mercury Interactive's software test management tool. It helps quality assurance personnel to plan and organize the testing process. With Test Director we can create a database of manual and automated tests, build test cycles, run tests, and report and track defects. We can also create reports and graphs to help review the progress of planning tests, running tests, and tracking defects before a software release.
Q11. Have you integrated your automated scripts from Test Director?
Ans: When we work with the WinRunner, we can choose to save the tests directly to the test director database or while creating a test case. In the Test Director we can specify whether the script in automated or manual, and if it is automated script then Test Director will build a skeleton for the script that can be later modified into one which could be used to test the AUT.
Q12. What are the different modes of recording?
Ans: There are two types of recording in WinRunner. They are
1) Context Sensitive Recording: In this recording it records the operations to perform on the application by identifying Graphical User Interface (GUI) objects.
2) Analog Recording: In this recording it Records keyboard input, mouse clicks, and the precise x- and y- coordinates travelled by the mouse pointer across the screen.
Q13. What is the purpose of loading WinRunner Add-ins?
Ans: Add-ins are used in WinRunner to load functions specific to the particular add-in to the memory. While creating a script only those funtions in the add-in selected will be listed in the function generator and while executing the script only those functions in the loaded add-in will be executed else WinRunner will give an error message saying it does not recognize the function.
Q14. What are the reasons that WinRunner fails to identify an object on the GUI?
Ans: WinRunner fails to identify an object in a GUI due to various reasons. The object is not standard windows object. If the browser uses in not compatible with the WinRunner version, GUI Map Editor will not be able to learn any of the objects displyed in the browser window.
Q15. What is meant by the logical name of the object?
Ans: An object's logical name is determined by its class. In most cases, the logical name is the lable that appears on an object.
Q16. If the object does not have a name then what will be the logical name?
Ans: If the object does not have a name then the logical name could be the attached text.
Q17. What is the difference between GUI map and GUI map files?
Ans: The GUI map is actually the sum of one or more GUI map files. There are two modes for organizing GUI map files. They are
1) Global GUI Map file: A single GUI map file for the entire application.
2) GUI map File per test: WinRunner automatically creates a GUI map file for each test created.
GUI map file is a file which contains the windows and the objects learned by the WinRunner with its logical name and their physical description.
Q18. How do you view the contents of the GUI map?
Ans: GUI map editor displays the content of a GUI map. We can invoke GUI map editor from the Tools Menu in WinRunner. The GUI map Editor displays the various GUI map files created and the windows and objects learned in to them with their logical name and physical description.
Q19. When do you create GUI map? Do you record all the objects or specific objects?
Ans: If we are learning a window then WinRunner automatically learns all the objects in the window else we will be identifying those objects, which are learned in a window, since we will be working with only those objects while creating scripts.
Ans: I have been using WinRunner for creating automated scripts for GUI, functional and regression testing for AUT.
Q2. Explain WinRunner testing process?
Ans: WinRunner testing process involves six main stages
1) Create GUI Map: Create File so that WinRunner can recognize the GUI objects in the application being tested.
2) Create test: Create test scripts by recording, programming, or a combination of both. While recording tests, insert checkpoints where we want to check the response of the application being tested.
3) Debug Test: Run tests in Debug mode to make sure they run smoothly
4) Run Tests: Run tests in verify mode to test the application
5) View Results: View Results determines the success or failure of the tests
6) Report Defects: If a test run fails due to a defect in the application being tested, we can report information about the defect directly from the Test Results window.
Q3. What is contained in the GUI map?
Ans: 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 phycical description. There are two types of GUI Map files.
1) Global GUI Map file: A single GUI Map file for the entire application.
2) GUI Map File per Test: WinRunner automatically creates a GUI Map file for each test created.
Q4. How does WinRunner recognize objects on the application?
Ans: WinRunner uses 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.
Q5. Have you created test scripts and what is contained in the test script?
Ans: 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. We can enhance the recorded test script, either by typing in additional TSL functions and programming elements or by using WinRunner's visual programming tool, the Function Generator.
Q6. How does WinRunner evaluate test results?
Ans: Following each test run, WinRunner displays the results in a report. The report gives details of all the major events that occured during the run, such as checkpoints, error messages, system messages or user messages. If mismatches are detected at checkpoints during the test run, we can view the expected results and the actual results from the Test results window.
Q7. Have you performed debugging of the scripts?
Ans: Yes, I have performed debugging of the 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.
Q8. How do you run the test scripts?
Ans: We run tests in Verify mode to test the 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.
Q9.How do you analyze results and report the defects?
Ans: Following each test run, WinRunner displays the results in a report. The report details all the major events that occured during the run, such as checkpoints, error messages, system messages, or user messages. If mismatches are detected at checkpoints during the test run, we can view the expected results and the actual results from the TestResults 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.
Q10. What is the use of Test Director Software?
Ans: Test Director is Mercury Interactive's software test management tool. It helps quality assurance personnel to plan and organize the testing process. With Test Director we can create a database of manual and automated tests, build test cycles, run tests, and report and track defects. We can also create reports and graphs to help review the progress of planning tests, running tests, and tracking defects before a software release.
Q11. Have you integrated your automated scripts from Test Director?
Ans: When we work with the WinRunner, we can choose to save the tests directly to the test director database or while creating a test case. In the Test Director we can specify whether the script in automated or manual, and if it is automated script then Test Director will build a skeleton for the script that can be later modified into one which could be used to test the AUT.
Q12. What are the different modes of recording?
Ans: There are two types of recording in WinRunner. They are
1) Context Sensitive Recording: In this recording it records the operations to perform on the application by identifying Graphical User Interface (GUI) objects.
2) Analog Recording: In this recording it Records keyboard input, mouse clicks, and the precise x- and y- coordinates travelled by the mouse pointer across the screen.
Q13. What is the purpose of loading WinRunner Add-ins?
Ans: Add-ins are used in WinRunner to load functions specific to the particular add-in to the memory. While creating a script only those funtions in the add-in selected will be listed in the function generator and while executing the script only those functions in the loaded add-in will be executed else WinRunner will give an error message saying it does not recognize the function.
Q14. What are the reasons that WinRunner fails to identify an object on the GUI?
Ans: WinRunner fails to identify an object in a GUI due to various reasons. The object is not standard windows object. If the browser uses in not compatible with the WinRunner version, GUI Map Editor will not be able to learn any of the objects displyed in the browser window.
Q15. What is meant by the logical name of the object?
Ans: An object's logical name is determined by its class. In most cases, the logical name is the lable that appears on an object.
Q16. If the object does not have a name then what will be the logical name?
Ans: If the object does not have a name then the logical name could be the attached text.
Q17. What is the difference between GUI map and GUI map files?
Ans: The GUI map is actually the sum of one or more GUI map files. There are two modes for organizing GUI map files. They are
1) Global GUI Map file: A single GUI map file for the entire application.
2) GUI map File per test: WinRunner automatically creates a GUI map file for each test created.
GUI map file is a file which contains the windows and the objects learned by the WinRunner with its logical name and their physical description.
Q18. How do you view the contents of the GUI map?
Ans: GUI map editor displays the content of a GUI map. We can invoke GUI map editor from the Tools Menu in WinRunner. The GUI map Editor displays the various GUI map files created and the windows and objects learned in to them with their logical name and physical description.
Q19. When do you create GUI map? Do you record all the objects or specific objects?
Ans: If we are learning a window then WinRunner automatically learns all the objects in the window else we will be identifying those objects, which are learned in a window, since we will be working with only those objects while creating scripts.
No comments:
Post a Comment