Running a Test Session

You can either use the Test Session window... to run a configured test session or you can run a saved test session using the API commands.

To run a test session from the Test Session window:

IMPORTANT:

A test session with multiple test cases generates many log messages and report measurements. Configure your Java plug-in memory to ensure that your machine allocates the appropriate amount of memory to the plug-in. If the plug-in is not configured with sufficient memory for a test, you will not be able to view all of the test measurements and you may receive "out of memory" errors. The Client Memory Monitor tracks memory usage.
The number of simultaneous test sessions that can be run on a test server is governed by the system capacity.
As you run a test , it will be assigned RUN ID (padded up to 4 Digits - 9999) which is unique in scope of live running tests on the TAS. START_TIME + RUN_ID is unique in the SCOPE of a TAS at any time. Test results will be indicated with a RUN ID + Iteration ID.

Open a test session...
Click Run to initiate the test session.

If the test system is able to use the assigned test servers and initialize the resources required for the test, the Logs tab is added to the Test Session window. The Reports tab is populated as soon as measurements are reported to the TAS.

If any of the assigned test servers has been reserved for this time by another user, the session is not initiated and a message is displayed with the user name of the reservation owner.

If the test system is unable to use the assigned test servers due to the test server status, a Test Server Status Warning message is displayed. If a test server is busy because it is running at its maximum capacity, you can re-assign the test cases that use that test server or wait until the test server is available. The System Status window displays the test sessions that a test server is currently hosting. A test server may also be unable to accept a test if it is in the process of being upgraded, or if it is in an unstable condition. You can view the status of a test server in the System Status window or the Test Server Administration window, and administrators can recycle the test server if necessary.

If one of the test servers used by the session is not running the software that was released with the TAS software, you will receive a warning stating that a test server is using non-default software and given the option to stop the test. This message will only appear once for each test session.

IMPORTANT:

You can manually select test procedures when certain test cases are running. A Command button is available to manually select the test procedures.

Running Multiple Test Cases on the Same Test Server:

Landslide resource allocation depends on the test case configuration of key parameters such as the number of mobile nodes and the transaction rate. As initialization is the most resource intensive part of a test, it is recommended starting large and resources affecting test cases first to minimize impact on tests that are already running.

See additional information in Reserving Ports for your Test Session.

NOTE: In a multiple test case environment, there is no priority assigned to the tests based on when they are started. All tests have equal access to the system resources. Each additional test case run on the same test server reduces the Test Server capacity by 20%.

Running a Test Session

Running Multiple Test Cases on the Same Test Server:

Learn about: