- Subscribe to RSS Feed
- Bookmark
- Subscribe
- Email to a Friend
- Printer Friendly Page
- Report Inappropriate Content
Creating and Editing Seed Data
|
CloudTest includes the ability to create repository-level seed data objects via the Central > Seed Data command in the top-level (blue highlighted) category. For new seed data objects, the Seed Data Wizard appears. This wizard is used to import data from a CSV or to create a seed data object and to enter new seed data manually. Seed data can be deployed using the Custom Properties tab in containers, clips, and tracks. Seed data is used to dynamically populate certain values in a test, either via a comma-separated value (CSV) file, or by creation of a new seed data object in CloudTest. Prior releases made limited seed data support available via the combined use of scripts and properties. Repository-level seed data support is in addition to prior support that was provided by the use of seed data scripts and a handful of settings for defining seed data slices, column counts, and row counts. As in prior releases, seed data can also be referred to via a URL, in which case settings can be maintained with respect to the source data (as a CloudTest repository object).Existing seed data objects are found in the Seed Data list and open in the Seed Data Editor. Users who refer to seed data by URL will find improved support as well. |
|
||||||
Seed data is queued so that each reference to the data (via a Custom Property) will access the data from a queue, rather than statically distributing the data to Custom Properties at Composition load time. Queuing decrease the likelihood that the end of seed data will occur and enables CloudTest to detect and act on the end of data. While distribution of seed data still occurs at the server level, which is determined per track within a composition, that data is no longer statically assigned at load time within each server. For example, when accessing seed data through a message, container, or clip, seed data values are allocated from the server’s queue at the time each item using the seed data comes into existence.The new method can potentially result in more efficient use of seed data, since the seed data is not allocated until an item that needs it actually comes into existence. This is particularly true when ramp ups are usedIn prior releases the seed data was statically allocated to all Tracks even though the Tracks at the end of the ramp up that start later might need less data, or perhaps even no data at all if the Composition ends before the Track even starts. |
|
||||||
Importing Seed Data from a CSVIn many cases, a comma-separated value (CSV) file may already be in use within an enterprise or may be easily exported to this format. Such a file can be used to send values to the server from different virtual users that CloudTest will run. A seed data file may contain simple name/value pairs, such as a user name/password list, or multi-column responses to a questionnaire, as well as many other types of information. |
|||||||
|
|
||||||
Click Next and the import begins. CloudTest will import the data found into its Repository and make it available for use in tests. If a key was entered for encryption, a prompt appears to enter it. Note that prior to entering the key the imported data is not displayed. |
|
||||||
|
Once the import completes, the Definition and Edit screen appears. Use the plus sign Add icon to add either a row or a column. Right-click to use a context menu to insert and delete columns or rows before or after a selection.
Creating or Editing Seed Data using the Editor
|
|






