When WinRunner is connected to a TestDirector (versions 7.5 or later only) project with version control support, you can update and revise your automated test scripts while maintaining old versions of each test. This helps you keep track of the changes made to each test script, see what was modified from one version of a script to another, or return to a previous version of the test script.
Note:A TestDirector project with version control support requires the installation of version control software as well as TestDirector’s version control software components. For more information about the TestDirector version control add-ins, refer to your TestDirector Installation Guide.
Adding Tests to the Version Control Database
When you add a test to the version control database for the first time, it becomes the Working Test and is also assigned a permanent version number. The working test is the test that is located in the test repository and is used by TestDirector for all test runs.
Note:Usually the latest version is the working test, but any version can be designated as the working test in TestDirector. For more information, refer to your TestDirector documentation.
To add a new test to the version control database:
Note:The Check In and Check Out options in the File menu are visible only when you are connected to a TestDirector project database with version control support, and you have a test open. The Check In option is enabled only if the active script has been saved to the project database.
If you have made unsaved changes in the active test, you will be prompted to save the test.
You can review the checked-in test. You can also run the test and view the results. While the test is checked in and is in read-only format, however, you cannot make any changes to the script.
If you attempt to make changes, a WinRunner message reminds you that the script has not been checked out and that you cannot change it.
Checking Tests Out of the Version Control Database
When you open a test that is currently checked in to the version control database, you cannot make any modifications to the script. If you wish to make modifications to this script, you must check out the script.
When you check out a test, TestDirector copies the latest version of the test to your unique checkout directory (automatically created the first time you check out a test), and locks the test in the project database. This prevents other users of the TestDirector project from overwriting any changes you make to the test.
To check out a test:
Note:The Check Out option is enabled only if the active script is currently checked in to the project’s version control database.
You should check a script out of the version control database only when you want to make modifications to the script or to test the script for workability.
Checking Tests In to the Version Control Database
When you have finished making changes to a test you check it in to the version control database in order to make it the new latest version and to assign it as the working test.
When you check a test back into the version control database, TestDirector deletes the test copy from your checkout directory and unlocks the test in the database so that the test version will be available to other users of the TestDirector project.
To check in a test:
Tip:You should close a test in WinRunner before using TestDirector to change the checked in/checked out status of the test. If you make changes to the test’s status using TestDirector while the test is open in WinRunner, WinRunner will not reflect those changes. For more information, refer to your TestDirector documentation.
WinRunner Related Interview Questions
|SILK TEST Interview Questions||LoadRunner Interview Questions|
|WinRunner Interview Questions||HTML Interview Questions|
|QTP Interview Questions||Manual Testing Interview Questions|
|OpenStack Interview Questions||Automation Testing Interview Questions|
|API testing Interview Questions||Rational robot Interview Questions|
|Selenium IDE Interview Questions||Performance Testing Interview Questions|
|Test Director Interview Questions|
Winrunner At A Glance
Understanding How Winrunner Identifies Gui Objects
Understanding Basic Gui Map Concepts
Working In The Global Gui Map File Mode
Editing The Gui Map
Merging Gui Map Files
Configuring The Gui Map
Learning Virtual Objects
Checking Gui Objects
Working In The Gui Map File Per Test Mode
Working With Web Objects
Working With Activex And Visual Basic Controls
Checking Powerbuilder Applications
Checking Table Contents
Creating Data-driven Tests
Synchronizing The Test Run
Defining And Using Recovery Scenarios
Handling Web Exceptions
Using Regular Expressions
Enhancing Your Test Scripts With Programming
Creating User-defined Functions
Creating Compiled Modules
Calling Functions From External Libraries
Creating Dialog Boxes For Interactive Input
Understanding Test Runs
Analyzing Test Results
Running Batch Tests
Running Tests From The Command Line
Controlling Your Test Run
Setting Properties For A Single Test
Setting Global Testing Options
Customizing The Test Script Editor
Customizing The Winrunner User Interface
Setting Testing Options From A Test Script
Customizing The Function Generator
Initializing Special Configurations
Integrating With Quicktest Professional
Managing The Testing Process
Testing Systems Under Load
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.