Silent Test Runner enables you to simulate the way a QuickTest test runs from LoadRunner and Business Availability Center. When you run a test using Silent Test Runner, it runs without opening the QuickTest user interface, and the test runs at the same speed as when it is run from LoadRunner or Business Availability Center At the end of the test run, you can view information about the test run and transaction times.
You can also use Silent Test Runner to verify that your QuickTest test is compatible with LoadRunner and Business Availability Center. A test will fail when run using Silent Test Runner if it uses a feature that is not supported by LoadRunner or Business Availability Center.
Note: You cannot run Silent Test Runner if QuickTest is already open or another test is currently running. You must close QuickTest and wait for its process to end before running your test using Silent Test Runner. You cannot use the ResultDir QuickTest environment variable when running a test from Silent Test Runner.
To run a QuickTest test using Silent Test Runner:
1. To open Silent Test Runner, choose Start > Programs > QuickTest Professional > Tools > Silent Test Runner. The Silent Test Runner dialog box opens.
2. Click the Browse button to navigate to your test. The Open Test dialog box opens and displays the tests located in your \Tests folder.
3. Select the test you want to run and click Open. The Open Test dialog box closes, the test name appears in the Test box of the Silent Test Runner dialog box, and the Run Test button is enabled. If you select a test that you ran previously, the Test Run Log and Transaction Summary buttons are enabled and you can display information about the last run of the selected test. The first time you run a test, the Test Run Log and Transaction Summary buttons are disabled.
4. Click Run Test to run your test. The test runs without opening the QuickTest user interface. The text Running test… appears next to the Run Test button while the test is running. After you start a test run, you cannot stop the test run from Silent Test Runner. If you close Silent Test Runner, the test continues to run. You can end a test by ending the mdrv.exe process.
5. When the test run finishes, the text Running test is replaced with the text Test run completed. If Silent Test Runner was unable to run your test, the text Test could not be run appears. If previously disabled, the Test Run Log button is enabled. The Transaction Summary button is also enabled if you ran a test with transactions and the button was previously disabled.
Viewing Test Run Information: Silent Test Runner provides test run information in log files. Each test generates a test run log, and any test with transactions generates an additional transaction summary.
Viewing the Test Run Log: The test run log is saved as output.txt in the \Tests\ folder. A log file is saved for each test run with Silent Test Runner and is overwritten when you rerun the test. To open the log file, click Test Run Log.
The log file displays information about the test run. For example, information is shown about each iteration, action call, step transaction, failed step, and so forth. Each line displays a message or error ID.
Viewing the Transaction Summary: The transaction summary is saved as transactions.txt in the \Tests\ folder. A transaction summary is saved for each test that includes transactions and is overwritten when you rerun the test. To open the log file, click Transaction Summary. The transaction summary displays a line for each transaction in the test. For each transaction, the status is displayed together with the total duration time and any wasted time (in seconds). The transaction measurements in Silent Test Runner are exactly the same as if the test was run from LoadRunner or Business Availability Center. A transaction summary is available only for a test that contains transactions ending with an EndTransaction statement. If a transaction started but did not end because of test failure, it is not included in the transaction summary.
Distributed transactions (transactions that start in one test and end in another) are not reported in the transaction summary but are included in the test run log.
Any transaction information included in the transaction summary is also included in the test run log.
Also See: Other LoadRunner Tutorials
Rahnuma is a technical content writer at software testing stuff. A software engineer by degree and a dynamic content creator by passion, she brings to table over 3 years of writing experience in tech niche. Combining her enthusiasm for writing and technology, she loves to share her thoughts on the latest tech trends.