Explore topic-wise InterviewSolutions in .

WR init file is WR INITIALIZATION file. In this file you can define global VARIABLE. So whenever you invoke WR it loads init file and SETS the global variable, provided you have to SET the PATH of the init file in option section. The default of init file is "mercury winrunner data slint".

WR init file is WR initialization file. In this file you can define global variable. So whenever you invoke WR it loads init file and sets the global variable, provided you have to set the path of the init file in option section. The default of init file is "mercury winrunner data slint".

Once the script is EXECUTED which has multiple checkpoints, the test results WINDOW shows detailed INFORMATION of WHETHER the checkpoint passed or failed. As we KNOW, checkpoints compare the expected results with the actual results, we can evaluate the result.

Once the script is executed which has multiple checkpoints, the test results window shows detailed information of whether the checkpoint passed or failed. As we know, checkpoints compare the expected results with the actual results, we can evaluate the result.

Two types of RECORDING method available in Win RUNNER

1.  Analog Recording
2. Context Sensitive

Two types of Recording method available in Win Runner

You can create a bitmap synchronization point that waits for the bitmap of an object or a window to appear in the application being tested.
During a test run, WinRunner suspends test execution until the SPECIFIED bitmap is redrawn, and then COMPARES the current bitmap with the EXPECTED one captured EARLIER. If the bitmaps match, then WinRunner continues the test.

Syntax:
obj_wait_bitmap ( object, image, time );
win_wait_bitmap ( window, image, time );

You can create a bitmap synchronization point that waits for the bitmap of an object or a window to appear in the application being tested.
During a test run, WinRunner suspends test execution until the specified bitmap is redrawn, and then compares the current bitmap with the expected one captured earlier. If the bitmaps match, then WinRunner continues the test.

Syntax:
obj_wait_bitmap ( object, image, time );
win_wait_bitmap ( window, image, time );

When a TESTER has completed the TESTING of a project and the AUT has been moved to production environment and been ACCEPTED by the stakeholders then the tester is released or SIGNED off from the project.

When a tester has completed the testing of a project and the AUT has been moved to production environment and been accepted by the stakeholders then the tester is released or signed off from the project.

An optional property is used only if the OBLIGATORY properties do not provide UNIQUE IDENTIFICATION of an OBJECT.

An optional property is used only if the obligatory properties do not provide unique identification of an object.

The TEST script NAME in the STARTUP Test BOX in the Environment tab in the General Options dialog box is the start up file in WinRunner.

The test script name in the Startup Test box in the Environment tab in the General Options dialog box is the start up file in WinRunner.

Parameterization is a CONCEPT in WR used to parameterize the DATA in AUT. Using parameterization, several data are provided to a single input value and tested. Parameterization LEADS to data DRIVEN test which in turn is used in doing STRESS testing.

Parameterization is a concept in WR used to parameterize the data in AUT. Using parameterization, several data are provided to a single input value and tested. Parameterization leads to data driven test which in turn is used in doing stress testing.

To store Batch test result
When you RUN a regular, interactive test, results are stored in a subfolder under the test. The same is true when a test is called by a batch test. WinRunner saves the results for each called test separately in a subfolder under the test. A subfolder is also created for the batch test that contains the overall results of the batch test run.

To view Batch test result
When a batch test run is COMPLETED, you can view information about the events that occurred during the run in the Test Results window. If one of the called tests fails, then the batch test is marked as FAILED.

The test log section of the Test Results window LISTS all the events that OCCUR red during the batch test run.
Each time a test is called, a call_test entry is listed in the log. To view the results of the called test, double-click its call_test entry.

To store Batch test result
When you run a regular, interactive test, results are stored in a subfolder under the test. The same is true when a test is called by a batch test. WinRunner saves the results for each called test separately in a subfolder under the test. A subfolder is also created for the batch test that contains the overall results of the batch test run.

To view Batch test result
When a batch test run is completed, you can view information about the events that occurred during the run in the Test Results window. If one of the called tests fails, then the batch test is marked as failed.

The test log section of the Test Results window lists all the events that occur red during the batch test run.
Each time a test is called, a call_test entry is listed in the log. To view the results of the called test, double-click its call_test entry.

• AUTO merge:- winrunner automatically handle if there EXIST any problem...suppose we have to merge THREE GUI map file of an application. In that two GUI map are same then in AUTOMATIC merge winrunner automatically handle this and take only one of them.user have no need to take pains for that.
• Manual merge:-in manual merging it SHOWS all the file and show target file having no file. We can manually select which file we want in manual file.
• merging is only done in GUI map file.

Use Web_Browser_Invoke(IE, URL); to invoke the BROWSER through the TEST script INSTEAD of OPENING the application.

Use Web_Browser_Invoke(IE, URL); to invoke the browser through the test script instead of opening the application.

See again it depends on the choice of the end user. If the user FEELS that the AUT is extensive and could really benefit from using WR and if there are plenty of Versions/Data DRIVEN Test/Regression CYCLES etc and it could be done with MINIMAL user interaction through WR, they can go for it.

See again it depends on the choice of the end user. If the user feels that the AUT is extensive and could really benefit from using WR and if there are plenty of Versions/Data Driven Test/Regression cycles etc and it could be done with minimal user interaction through WR, they can go for it.

You first unit-test each procedure by feeding it appropriate test data, observing the outcome, and RETESTING as needed to make sure the BUG fixes contain no new errors. Unit-testing a stored procedure involves a series of test-debug-retest CYCLES. The NUMBER of cycles will depend on your company's defect tolerance, your application's release date, and, of COURSE, the "bugginess" of your code.

You first unit-test each procedure by feeding it appropriate test data, observing the outcome, and retesting as needed to make sure the bug fixes contain no new errors. Unit-testing a stored procedure involves a series of test-debug-retest cycles. The number of cycles will depend on your company's defect tolerance, your application's release date, and, of course, the "bugginess" of your code.

• We need JAVA addin in winrunner to RECOGNIZE java UI objects as standard objects.
• By DEFAULT mercury winrunner only RECOGNIZES Microsoft’s UI objects.

you can execute your TEST in c compiler with WINDOW RUN command as TSL is c BASED language.

you can execute your test in c compiler with window run command as tsl is c based language.

• A batch test is a script that CONTAINS call statements to other TESTS. A batch test is created by SELECTING the "Run in batch mode" from the run tab in the Tools-->GENERAL Options.
• A batch test runs as a regular test.
• The only difference being that all messages like pause, wait...ETC are suppressed in a batch test so that the test runs without interruption.
• Winrunner opens and executes easc called test.

• SYNCHRONIZATION is represented as "INTELLIGENT Wait Statement"
• It starts SEQUENTIALLY while TSL Script is executed.
• WAITS till the defined objects property is CHANGED and ends accordingly.

There are two types of METHODS: subroutines and functions. Ideally, each FUNCTION or subroutine will PERFORM a distinct, logical task. Functions are very similar to subroutines their syntax is nearly IDENTICAL, and they can both perform the same actions. Functions, however, return a value to the code that CALLED it.

There are two types of methods: subroutines and functions. Ideally, each function or subroutine will perform a distinct, logical task. Functions are very similar to subroutines their syntax is nearly identical, and they can both perform the same actions. Functions, however, return a value to the code that called it.

If we want to run the recorded script in WIN RUNNER we should have store GUI map file if there is any CHANGES in the object the win runner cannot recognize the object so we have to LEARN the object once again and update the gui file and reload the file.

If we want to run the recorded script in win runner we should have store GUI map file if there is any changes in the object the win runner cannot recognize the object so we have to learn the object once again and update the gui file and reload the file.

SYNCHRONIZATION ERROR will OCCUR.

Synchronization Error will occur.

WINRUNNER learns custom class OBJECTS under the generic “OBJECT” class. WinRunner records operations on custom objects USING obj_ statements.

WinRunner learns custom class objects under the generic “object” class. WinRunner records operations on custom objects using obj_ statements.

There are two functions which can be USED for reporting the MSG.

1) report("msg");
2)tl_step("TOTAL",1,"msg");
where 1ST arg is the name of the box, 2nd arg is the status 1 for fail and 0 for pass and 3rd is the msg which you WOULD like to give.

There are two functions which can be used for reporting the msg.

1) report("msg");
2)tl_step("total",1,"msg");
where 1st arg is the name of the box, 2nd arg is the status 1 for fail and 0 for pass and 3rd is the msg which you would like to give.

Nobody will write test CASES in WinRunner. Just we will write the Test SCRIPT for a corresponding test CASE. Initially we write all manual test cases. We will write the test scripts for the corresponding test cases.

Nobody will write test cases in WinRunner. Just we will write the Test Script for a corresponding test case. Initially we write all manual test cases. We will write the test scripts for the corresponding test cases.

• Back ground SCREEN
• TAB order
• RESOLUTION
• No.of ELEMENTS in the screen

Generally Win Runner is suitable for the following APPLICATIONS:

1. WEB applications
2. Power Builder applications
3. Visual BASIC applications
4. ACTIVEX CONTROL applications

Generally Win Runner is suitable for the following applications:

In Winrunner we use GUI Map configuration to map the Custom OBJECT to the Standard Object.

Virtual Object WIZARD: we use this when winrunner is UNABLE to RECOGNIZE as a Object we forcely instruct winrunner to Recognize it as an Object.

In Winrunner we use GUI Map configuration to map the Custom object to the Standard Object.

Virtual Object Wizard: we use this when winrunner is unable to recognize as a Object we forcely instruct winrunner to Recognize it as an Object.

When any bug has COME then bug or defect in WINRUNNER is SENT VIA e-mail to the quality assurance MANAGER, who tracks the defect.

When any bug has come then bug or defect in winrunner is sent via e-mail to the quality assurance manager, who tracks the defect.

The purpose of the commands is:

• STEP--> Runs a SINGLE line of the TSL SCRIPT.
• STEP INTO--> CALLS and displays another test/user-DEFINED function.
• STEP OUT-->Used in conjunction to STEP INTO and completes the EXECUTION of the called test/user defined function.
• STEP TO CURSOR-->Runs a selected section of the script

The purpose of the commands is:

You can use Data Junction to create a CONVERSION file which CONVERTS a DATABASE to a target TEXT file.

You can use Data Junction to create a conversion file which converts a database to a target text file.

CLICK on corresponding add in Manager (Web,....) at the TIME of enter to the winrunner then application and test.

Click on corresponding add in Manager (Web,....) at the time of enter to the winrunner then application and test.

In MAIN test all the functions should be written in the script and in the COMPILE module we will just GIVE the functions in one script and compile that and whenever we want that functions we can call that by using call statement. This is very easy because no. of users can use this call statement without repeating the same FUNCTION once again.

In main test all the functions should be written in the script and in the compile module we will just give the functions in one script and compile that and whenever we want that functions we can call that by using call statement. This is very easy because no. of users can use this call statement without repeating the same function once again.

ACCORDING to your PROJECT you can use the repository. i.e according to the oracle version you are USING the repository is to be set.

According to your project you can use the repository. i.e according to the oracle version you are using the repository is to be set.

tl_step will DRIVE the script into sections & inserts a status MESSAGE in the last report for previous section. In tl_step we can set WHETHER the action is passed or failed.

Report_msg is used to write a message in the test results.

tl_step will drive the script into sections & inserts a status message in the last report for previous section. In tl_step we can set whether the action is passed or failed.

Report_msg is used to write a message in the test results.

An object’s LOGICAL name is determined by its CLASS. In most CASES, the logical name is the label that appears on an object.

An object’s logical name is determined by its class. In most cases, the logical name is the label that appears on an object.

SELECT FILE menu / TEST Properties, click on Test PARAMETERS Tab then click on Add button to create a PARAMETER. You need to pass a value while calling this script.

Select File menu / Test Properties, click on Test Parameters Tab then click on Add button to create a Parameter. You need to pass a value while calling this script.

We can ALSO CONNECT using db_connect("ses", "DSN") to GET complete control on DB.

We can also connect using db_connect("ses", "dsn") to get complete control on DB.

When you do the testing in the PROJECT just we can check the FUNCTIONALITY how to WORK the project here we can’t test the CODE just how it works this module.

When you do the testing in the project just we can check the functionality how to work the project here we can’t test the code just how it works this module.

The command used to COMPARE two files in WIN Runner is:

The command used to compare two files in Win Runner is:

STOP : stops the SCRIPT from Execution
PAUSE : pauses at that POINT in execution. Now ONE can use checkpoints to know the value of that parameter. But you have to use “pause" also. It’s like this : use CP and use Pause st.

Stop : stops the script from Execution
Pause : pauses at that point in execution. Now one can use checkpoints to know the value of that parameter. But you have to use “pause" also. It’s like this : use CP and use Pause st.

• During the WinRunner Launching, Click the CHECK BOX "ON" for Web Test in addins manager.
• A HTML page contains all OBJECTS and static text data in rows, COLUMNS, TABLES and grids which are not visible to users physically.
• Then record the operations and create the check points in Winrunner and execute the test.

• COMPILED module is a script containing a library of user-defined functions that you WANT to call frequently from other tests. When you load a compiled module, its functions are automatically compiled and remain in memory. You can call them directly from within any TEST.
• Compiled modules can improve the organization and performance of your tests. SINCE you debug compiled modules before using them, your tests will require less error-checking. In ADDITION, calling a function that is already compiled is significantly faster than interpreting a function in a test script.

There is no WIZARD to REMOVE DDT, you NEED to remove MANUALLY the FOLLOWING statements

ddt_open, ddt_get_row_count, ddt_set_row, ddt_val, ddt_close

There is no Wizard to remove DDT, you need to remove manually the following statements

ddt_open, ddt_get_row_count, ddt_set_row, ddt_val, ddt_close

QuickTest PROFESSIONAL 8.2 CONTAINS the following new features: The new Business Component Keyword View helps you design your components quickly and easily, in a self-documenting tabular user interface that requires no programming knowledge. The Business Component Keyword View is similar in APPEARANCE and functionality to the Steps tab in the Business Components module in Quality Center. This enables both QuickTest and Quality Center users to see the same component content. The new Function Definition Generator enables you to quickly document and register new user-defined functions for tests and components. A new Documentation Only option in the Keyword View enables you to view and print the auto-documentation INFORMATION for tests or components. For example, you may want to view and print the step descriptions displayed in the Documentation column as instructions for manual testing. QuickTest provides a new parameter type-local parameter. A local parameter enables you to parameterize an input value for a step, or to output a run-time value to a parameter. Local parameters are accessible only to the current business component. You can now create multiple application areas and use a different application area for each part of your application. Each application area specifies the resources and settings that can be used by a component. QuickTest provides you with a set of predefined resource files that you can associate with an application area or a specific component for additional functionality. You can find additional QTP 8x also makes easy of data driven for encrypted data

QuickTest Professional 8.2 contains the following new features: The new Business Component Keyword View helps you design your components quickly and easily, in a self-documenting tabular user interface that requires no programming knowledge. The Business Component Keyword View is similar in appearance and functionality to the Steps tab in the Business Components module in Quality Center. This enables both QuickTest and Quality Center users to see the same component content. The new Function Definition Generator enables you to quickly document and register new user-defined functions for tests and components. A new Documentation Only option in the Keyword View enables you to view and print the auto-documentation information for tests or components. For example, you may want to view and print the step descriptions displayed in the Documentation column as instructions for manual testing. QuickTest provides a new parameter type-local parameter. A local parameter enables you to parameterize an input value for a step, or to output a run-time value to a parameter. Local parameters are accessible only to the current business component. You can now create multiple application areas and use a different application area for each part of your application. Each application area specifies the resources and settings that can be used by a component. QuickTest provides you with a set of predefined resource files that you can associate with an application area or a specific component for additional functionality. You can find additional QTP 8x also makes easy of data driven for encrypted data

win_activate has the format win_activate(window);. The win_activate function makes the specified window the active window by bringing it into focus & raising it to the top of the display. (It is the equivalent to clicking on the window banner)

Set_window has the FOLLOWING format: set_window(window,[time]); The set_window function directs input to the correct application window. This directs the GUI map to this window. It also sets the scope for object identification in the GUI map.

The most important difference is that set_window has a timing OPTION. WinRunner will wait a maximum of the number used in the function, PLUS the system set TIMEOUT, to wait for the window to APPEAR. Win_activate assumes the window is already on the desktop and has no timing option.

win_activate has the format win_activate(window);. The win_activate function makes the specified window the active window by bringing it into focus & raising it to the top of the display. (It is the equivalent to clicking on the window banner)

Set_window has the following format: set_window(window,[time]); The set_window function directs input to the correct application window. This directs the GUI map to this window. It also sets the scope for object identification in the GUI map.

The most important difference is that set_window has a timing option. WinRunner will wait a maximum of the number used in the function, PLUS the system set timeout, to wait for the window to appear. Win_activate assumes the window is already on the desktop and has no timing option.

"To capture selected area VALUE into variable for screen area OPTION in text checkpoint (get text)."

syntax: obj_get_text ("screen area NAME",variable,x1,y1,x2,Y2);

"To capture selected area value into variable for screen area option in text checkpoint (get text)."

syntax: obj_get_text ("screen area name",variable,x1,y1,x2,y2);

If you WANT CALL DLL FILE through Winrunner, you should use api controls it is a special functions.

If you want call dll file through Winrunner, you should use api controls it is a special functions.

The CLASS of a function can be either static or public.

•  A static function is available only to the test or module within which the function was defined.
•  Once you EXECUTE a public function, it is available to all tests, for as long as the test containing the function remains OPEN. This is convenient when you want the function to be accessible from called tests. However, if you want to create a function that will be available to many tests, you should PLACE it in a compiled module. The functions in a compiled module are available for the duration of the testing SESSION.
•  If no class is explicitly declared, the function is assigned the default class, public.

The class of a function can be either static or public.

There are lot of differences in winrunner and QTP.

1. Winrunner does not SUPPORT the runtime OBJECTS during recording, but QTP SUPPORTS that thing.
2. winrunner should not supports XML,.NET APPLICATIONS, but QTP supports.
3. winrunner script is like c-language, but QTP is like VB.
4. CHECK points are more compared to QTP.

There are lot of differences in winrunner and QTP.

You cannot RUN Unix SHELL SCRIPTS in Winrunner COMMANDS, because Winrunner is Windows based.

You cannot run Unix shell scripts in Winrunner commands, because Winrunner is Windows based.

We don't TEST the MOBILE APPLICATION using WinRunner. Because it involves some protocols for data transmission. That is why we need some DIFFERENT type of tool for testing the protocols or we can do MANUALLY.

We don't test the mobile application using WinRunner. Because it involves some protocols for data transmission. That is why we need some different type of tool for testing the protocols or we can do manually.