Split a test

+

Search Tips   |   Advanced Search

 

Overview

With the test-splitting capability, you can record a long scenarios with many functional steps against an application and then, in the editor, dissect the test into many smaller test segments, which you can run in various orders in a schedule.

The wizard determines which variables need to persist among the split tests and creates linkages.

Split tests BEFORE creating, adding, and associating datapools.

Split a test

1. Double-click a test

2. Select one or more contiguous elements in the test for splitting into a new test.

   You can select all elements, except for variable containers, that are immediate children of the root node of the test.

3. Right-click the selected elements, and then select...
   Save Selection As New Test

   

4. In the Save Selection as New Test window, type a file name for the new test, and optionally provide a description or comment for the split test.

   

   1. To add the Description/comment field as a comment at the beginning of the split test, check...

      Also use description text for comment at beginning of each test

   2. To mark the selection in the original test with marks of the form [N-> where N is a positive integer that corresponds to the number of saved selections.

      Mark the selection in the editor

      Selections saved as a new test are marked with the identifier: [1->.

      

      If you save three selections, the original test is marked with these identifiers:

      • [1->
      • [2->
      • [3->

   3. Click Next.

   Editor marks are removed when the test is closed. You cannot save marked test elements.

   Right-click and select Clear Range to remove the marks before closing the test.

   

5. On the next page of the Save Selection as New Test wizard, confirm changes...

   

   Typically, you leave the following selected...

   • Link tests through variables
   • HTTP Specific Changes selected

   Clearing these options might make a split test unusable or produce unpredictable results. However, you can clear specific Link tests through variables boxes if you do not want certain data to be correlated between the tests.

6. Click Finish.

Results

The new test is created from the selected elements. The test variables created by splitting a test are listed in the container...

Variables Created by Split Test

Verify variables are created and assigned with values by a test executed before the newly split test.

For more information on test variables...

• About test variables
• Declare and assign test variables

The original test is marked if you select the option...

Mark the selection in the editor option

To remove the marks, right-click the selected elements in the original test and select...

Clear Range

You are also prompted to delete the new test. Click Yes to delete the new test or No to preserve it.

Example: Split test into four parts

Assume that the visitIBM recorded test contains the following actions:

• Log on to a server.
• Create an entry on the server and remove the entry.
• Edit an entry, validate that the change occurred, and restore the entry.
• Log off of the server.

You want to split the test into four parts:

1. Logon
2. Create
3. Edit
4. Logoff

You need to split the test four times.

• Open visitIBM and select the logon actions. Name the new test Logon, which contains the Logon actions.

• Select the create actions. Name the new test Create.

• Select the edit actions. Name the new test Edit.

• Select the logoff actions. Name the new test Logoff.

You then create a schedule that runs virtual users selected from a datapool.

For the logon test for example, make sure to assign user/password variables in the Test Variables section.

Each virtual user runs the Logon test, performs various combinations of the Create and Edit tests, and finally runs the Logoff test.

Be aware, however, that when you split the tests, the Create test might have initialized variables that the Edit test uses. Therefore, if you reverse the order during the run (that is, run the Edit test before the Create test), make sure that the variables that the tests share are initialized and set correctly.

Related

1. HTTP test editor overview
2. Define performance requirements in tests
3. Add an authentication folder
4. Verify expected behavior
5. Cookies - How loops affect the state of virtual users
6. Split a test page
7. Merge test pages
8. Disable and enable secondary HTTP requests
9. Reuse tests on different hosts: Server connection variables
10. View a test in the Protocol Data view
11. Test Siebel applications
12. Split a test during recording