What are data driven tests?
While testing the application, the data driven tests are used to check how the application performs the same operation with various sets of data.
While testing the application, the data driven tests are used to check how the application performs the same operation with various sets of data.
GUI spy is used to view the properties of the GUI object in the Desktop. The Spy pointer can be used to point at an object and the GUI spy displayes theier values and properties in the GUI spy dialog box.
Selecting the multiple objects can be done by using the Shift key and/or the Control key to select multiple objects. To select all objects in a GUI map file use choose Edit > Select All.
While loading the GUI map file, all the information about objects and windows with the physical description and logical names will get loaded in the memory. Whenever the winrunner executes the script, the objects will get identified using the information already loaded in the memory.
The logical name in an object is said by its class. Most of the time, the logical name is the label that appears on an object.
In winrunner after a test run, the test results will get displayed in a report. All the major actions during the run like Checkpoints, Error messages, System messages will be displayed in the report. The mismatches in checkpoints during the test run can be viewed as expected results and actual results in Test results window. The information about a test run fail due to defect can also be reported to others through test results window.
To test the application it should be run on the verify mode, Winrunner run into a checkpoint in the test script, after that it compares the current data being tested with the expected data captured before. Winrunner displays the mismatches as the actual results.
To debug the Test scripts, it should be executed in the Debug Mode. Otherwise by using the functionalities like Step, Step Into and Step out we can debug the test script.
The Test Scripts is nothing but the statements in Mercury Interactive’s Test Script Language (TSL). In test window these statements show as a test script, the recorded test scripts can be enhanced by adding some TSL functions and programs or using the Winrunner visual programming tool, that’s the Function Generator.
At the end of every test run, the test results are displayed in a report in Winrunner. The details of the report contains all the main events took place through the run like error messages, user messages, system messages or checkpoints. The mismatches found at Checkpoints during the test run can be viewed in the Test results window with Expected results and Actual results.
The GUI map is mainly used to store the information it learned about a particular window or an object. When running the test in Winrunner, the GUI map is b used to identify the objects. It first reads the description of a object and searches for an with the same description or properties.
The two types of GUI map files, they are,
Global GUI Map file: a single GUI map file is used for the entire application.
GUI Map File per Test: a GUI Map file is automatically created by Winrunner for each test created.
Synchronization points helps to solve the expected timing problems between your application and the test. For a database application test, the synchronization point can be added which makes the test to wait until that particular database records get loaded on the screen.
Checkpoints is used to compare the current behavior of the application being tested to its behavior in an earlier version.
Four types of checkpoints can be added to test scripts, they are,
GUI checkpoints verify information about GUI objects. Ex, you can check that a button is enabled or see which item is selected in a list.
Bitmap checkpoints take a “snapshot” of a window or area of your application and compare this to an image captured in an earlier version.
Text checkpoints read text in GUI objects and in bitmaps and enable you to verify their contents.
Database checkpoints check the contents and the number of rows and columns of a result set, which is based on a query you create on your database.
GUI Map File Creation: By creating GUI Map file the WinRunner can identify the GUI objects in the application going to be tested.
Test scripts Creation: This process involves recording, programming or both. During the process of recording tests, insert checkpoints where the response of the application need to be tested.
Debug Test: Run the tests in Debug mode to make sure whether they run smoothly.
Run Tests: Run tests in Verify mode to test the application.
View Results: This determines the success or failure of the tests.
Report Defects: If a particular test run fails due to the defect in the application being tested, defects can be directly reported through the Test Results window.