Relevant for: GUI tests only
Silent Test Runner enables you to simulate the way a test runs from LoadRunner, Performance Center, and Business Service Management. When you run a test using Silent Test Runner, it runs without opening the UFT user interface, and the test runs at the same speed as when it is run from LoadRunner, Performance Center, or Business Service Management 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 test is compatible with LoadRunner, Performance Center, and Business Service Management. A test will fail when run using Silent Test Runner if it uses a feature that is not supported by these products.
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.
The test run log is saved as output.txt in the <Unified Functional Testing>\Tests\<test name> 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. For details on message and error codes in the log file, see your Performance Center or Business Service Management documentation.
The transaction summary is saved as transactions.txt in the <Unified Functional Testing>\Tests\<test name> 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, Performance Center, or Business Service Management.
For details on generating silent runs, see Silent Test Runner Dialog Box.