It sounds like you're trying to solve two challenges with the same data. One, load testing and two, unit testing. Technically, if you're needing to make substantial changes to your data, you are actually performing more than one test and each test should be considered unique and generate its own set of test data.
On a decent computer with a quad processor, GenRocket generates about 15,000 rows per second, which is 900,000 rows per minutes or 54,000,000 rows per hour. So, it is possible to do load testing by creating different GenRocket scenarios to produce different data results quickly. It all depends on how much data you need to perform your load tests.
That being said, there are ways you can substantially modify your data after it has been generated. You can write your own SQL statements to make changes or you can write scenarios that will use specific receivers to create update statements and execute them on the database (we will be adding a SQL Update Receiver in our next release).
However, the best approach would be to treat each test as a separate GenRocket Scenario. Solve one challenge at a time. It's what GenRocket is designed to do.
Are the Receivers GenRockt specific artifacts? i'll have to look that up.
Hycel Taylor Iii
Joined: Feb 24, 2014
Receivers are the component in GenRocket that morphs generated data into a useable format.
For example, lets say you created a User Domain with the usual Attributes (.e.g Id, lastName, firstName, etc.), you want to generate 100,000 users and you want to have the generated data in three different formats CSV, XML & SQL. In GenRocket you would attach a three receivers to your User Domain, DelimitedFileReceiver, XMLFileReceiver and SQLFileReceiver. When you run your Scenario, each Receiver will morph the generated data into its given file format.