Disclaimer: This scenario is not specifically tested as part of testing tools product development and thus is not officially supported, but we wanted to share that customers have been successful using these techniques.
Note: This “tips and tricks” document assumes the audience has familiarity with running singular Web UI tests through the Quality Manager Adapter, including how to start and stop the adapter from within the desktop client.
The Functional Test Web UI perspective offers a feature called “Run Distributed Tests”. The feature is accessed by selecting multiple tests in the Test Navigator panel.
Right-click to select “Run Distributed Test”. Both tests run at the same time.
If tests are being run directly from the desktop client, this works fine. There are also IBM Knowledge Center instructions for running from a command line on the desktop client machine.
The recipe for success becomes more complex if the tests are to be run from a remote RQM/ETM TestCase or TestSuite through the Functional Test Web UI Quality Manager Adapter. That scenario was recently investigated in response to a customer inquiry.
Execution from the Desktop Client
Note: IBM Rational Quality Manager (RQM) is now known as IBM Engineering Test Manager (ETM). The abbreviations RQM and ETM are equivalent within this document.
The difficulty in running simultaneous Web UI tests through the Quality Manager Adapter lies in the way test execution details are transmitted between RQM and the testing tool. In simplified terms, RQM runs a test by passing a message through the adapter: “Run one test asset of this specific type from this location with these parameters”. If the RQM TestSuite involved multiple WebUI tests, the same type of request is serialized and each test will be run in sequence. There is no capacity to alter the message to something like: “Run N test assets of these specific types from these locations with these parameters”.
There is a limited solution that allows you to run multiple Web UI tests simultaneously from RQM.
Requirement: the performance test tool must be installed alongside the functional test tool in a “shell-shared” configuration.
Eclipse is a tool in which functionality is based on perspective. Different perspectives allow access to different functions and, in this case, different test assets. In working with Web UI tests, the focus is in the Web UI Test perspective.
Installing the performance test tool provides access to the Performance Test perspective.
The File > New menu from the Web UI Test perspective:
The File > New menu from the Performance Test perspective:
There is some overlap but what the addition of the Performance Test perspective allows is the creation of a new VU Schedule (in performance test parlance, VU is virtual user). VU Schedules are used to drive performance tests by setting user loads, which agents to use, playback rates and many other details related to performance tests, but none of that matters for this discussion. What is important is that VU Schedules are a test asset that allows multiple tests to run at the same time.
Here are the steps to run multiple tests at the same time from RQM.
- Move to the Performance Test Perspective.
- Create a new VU Schedule (File > New > VU Schedule).
- Provide a File name. Click the Next button.
- Set the number of users to the number of Web UI tests to be run concurrently. This is where the concept of LIMITED workaround comes into play. Without VU licenses in place, this number CANNOT exceed 5. Attempting to run a schedule with more than 5 users without the necessary VU licenses results in a licensing error. Click the Finish button.
- Use the Add button to add more user groups.
- Repeat until the number of User Groups is equal to the number of Web UI tests to run.
Note the initial User Group uses percentage-based user allocation while subsequent User Group entries are set to 1 user.
That first User Group setting must be modified.
- Click on “User Group 1” and set the Absolute value to 1.
- Click the Add button and select Test.
- Choose one of the Web UI tests and click OK. Repeat until there is at least one Web UI test assigned to each User Group.
For localized validation of the concept, click the Run VU Schedule button and watch as the tests run simultaneously. Of course one may run in front of the others on the deskop.
Execution from RQM/ETM
Disclaimer: This document is NOT being developed by RQM/ETM support. The examples use RQM version 6.0.6 and other versions may differ in functionality.
Having the performance test tool and the functional test tool in an Eclipse shell-share generates TWO adapter entries on the Execution > Adapter Console menu:
One (RPT on … ) represents the performance tester, the other (RTW on …) represents the functional tester.
The two entries have the same Machine Name and IP address. In actuality, they are the same adapter, but the Adapter type is important because it controls what types of test assets are visible on the client (testing) machine.
If there are not two entries, something isn’t properly set up with the adapter. The first thing to check is the adapter.config file (default: C:\Program Files\IBM\SDP\RPT-RST_RQMAdapter\config\adapter.config).
The top two lines correspond to the listing in the RQM Adapter Console. If there are not two lines, there will not be two adapters listed on the RQM side. Correcting that may require uninstall/reinstall of “missing” testing product to ensure shell-share installation is in place.
If all in is in order, the only additional step is to create an RQM Test Script of type “Rational Performance Tester”.
When selecting the adapter to use, select the RPT adapter.
When selecting the testsuite to import, select the appropriate VU schedule from the list of testsuite files.
Note that “testsuite” is a file extension used by many different types of test assets (tests, schedules, compound tests) so it is important to provide meaningful names to test assets used in the testing tool.
Running the Adapter from the Command Line
Situations may arise where keeping the Eclipse IDE active is not possible. The same functionality can be accomplished by starting the adapter from the test machine using the command line interface.
In the “Execution from RQM” section above, the adapter.config file (default location C:\Program Files\IBM\SDP\RPT-RST_Adapter\config) was mentioned. Provided all the fields in this file are properly populated, one can make use of the command line interface.
- Open a command prompt window (cmd).
- Navigate to RPT-RST_RQMAdapter\bin directory.
- Run this command:
The adapter can be stopped using the command: .\RQMAdapter stop
Note: While this technique is not officially supported, it is successful within the documented limitations.
#2019 Year in Review