A test must contain a reference to any datapool that it uses.
All projects in your workspace are searched using the regular expression shown in the Pattern box. With the default pattern (shown in the box), all datapools in all projects are found and any that you have not previously added to this test are listed in Matching Resources.
The In Folders box lists the project in which the datapool you selected resides. Its columns are listed by name in the Columns box and the Name box displays the simple name of the datapool. (The simple name is displayed by the Test Navigator: regular navigators display the full name with extension displayed under Matching Resources.)
Option | Description |
---|---|
Shared (per machine) (default) | Virtual users on each machine draw from a shared view of the datapool, with datapool rows apportioned to them collectively in sequential order, on a first-come-first-served basis. This choice makes it likely that the virtual users or loop iterations will use data from different rows and that the server will see variable data. The exact row access order among all virtual users or iterations cannot be predicted because this is dependent on the test execution order and duration on each machine. |
Private | Each virtual user draws from a private view of the datapool, with datapool rows apportioned to each in sequential order. This choice offers the fastest test execution and assures that each virtual user gets the same data from the datapool in the same order, but it is the choice most likely to result in different virtual users using the same row. With this choice, rows of a datapool will increment only if you add the test(s) using the datapool(s) to a schedule loop with more than one iteration. |
Segmented (per machine) | Virtual users on each machine draw from a segmented view of the datapool, with data apportioned to them collectively from their segment in sequential order, on a first-come-first-served basis. The segments are computed based on how a schedule apportions virtual users among machines. For example, if a schedule assigns 25% of users to group 1 and 75% to group 2, and assigns these groups to machine 1 and machine 2, the machine 1 view will consist of the first 25% of datapool rows and the machine 2 view will consist of the remaining 75% of rows. This is a good choice where it's important to prevent virtual users from selecting duplicate values (for example, account IDs). If you disable wrapping, no row can be used more than once. Note: this
choice requires that the datapool contain only one equivalence class. With
the other choices, equivalence classes are ignored.
|
Parent topic: Providing tests with variable data