Data Generation: Going Beyond The Database by Gregg Bolinger on Nov 13, 2013

When people talk about data generation, whether it is test data, demo data, or program data, they usually think in terms of the database. That’s where we store all of our data so that is what we need to generate data for. This is very true. Probably the majority of times I’ve needed to generate data I needed it for a database. And GenRocket is good at generating database data. It is just as good at generating non-database data.

At its core, GenRocket generates data. The data doesn’t care where it goes. What matters is what Receivers are assigned to the Domain. Receivers “receive” data generated by a Generator, consume that data, morphs it into a specific format (as defined by the Receiver), and delivers the data to a final destination. That might be an XML file, JSON, or a delimited file (csv).

One of our goals with GenRocket is to allow it to be integrated easily with any process. We’re not trying to change how you get your work done. We just want GenRocket to speed up the process.

Do you create test data in a spreadsheet by hand? Let GenRocket create the spreadsheet for you. Do you need external config files for JMeter? Let GenRocket generate the CSV files for you. How many times have you waited on the server side engineers to provide you with JSON data for your JavaScript front end? Let GenRocket generate the JSON for you. Need data in your database? Noticing a pattern here?

You don’t have to change and you can speed up your process!

We’re constantly coming up with new Receivers to add to GenRocket’s core set. A couple of WebService Receivers are coming soon. We want to hear your ideas. Where does your data need to go? What kind of Receivers would you like to see in GenRocket? Let us know in the comments are by contacting