Ahh.... just read the release notes for version 2.1.
the DataGen step will remain in the product, but will not evolve.
With this, i think it is safe to use DataGen for templating purpose.
Hi richie,
no i am not sure, that's the reason why i was asking the community. :-)
With DataGen, there is explicitly the possibility to create Templates:
A template property lets you create complex multi-line values. It is useful when you generate a request body.
Tip: A template can also contain property expansions. So you can use other properties of the test step.
After beeing deprecated, the docu recommends the following replacement:
Template DataGen does not have a direct alternative. If you need to simulate it in your tests, generate the values with the DataSource test step and add them to the request by using property expansions.
Within the DataSource, i can use Generators to generate different type of pre defined values (Address, Phone Number, GUID, ...) and "Custom Strings". But these are only single line strings, as DataSource generally is intended to act like a database which generates rows of data.
The "Properties" test step could be a suitable replacement, as it defines static key/value pairs. But unfortunately, the values are also only single line and there is no property expansion within the values.
So with DataGen beeing deprecated, i can't find any posibility to define a single multiline (template like) property to be passed to my test step.
Regards, Joachim
Mithotyn, Firstly do I agree with you that I don't feel the DataSource test is an inferior replacement. My main issue is that the DataGen test step is so simple to use. By the sounds of it we make similar use of it to generate complex data that can be simply referenced as a property, where we are different is I almost exclusively use the Groovy script option.
I will usually group together a collection of related but independent properties into a single DataGen step. With the Groovy Data Source (as recommended by the documentation) you only have a single script for all the properties you define. Thus you end up with a single script that has to generate all the properties (I feel this just makes things confusing and harder to maintain), or you have multiple Groovy Data Source each with one property (bloating your test case).
The Data Source test step seems to work very well for looping sets of data (I have in fact used the Groovy Data Source very successfully for looping through data), but not when you want specific data values, e.g. scenario specific data. It feels like the Data Source test step is a suitable replacement for the DataGen list, or DataGen number (using a Data Generator source). But then the DataGen Script and DataGen Template were shoe-horned in. I'll just repeat that I think the DataGen test step is simpler to use and maintain.
I don't think the DataGen test step is going anywhere soon, while it was deprecated in version 2.0 it was actually enhanced in version 2.1 I also would really hope that if it actually was going to be removed then we would get advance notice of it's specific removal, not just have it disappear in a new version! Rightly or wrongly I'm still using them.
All that being said Mithotyn if you really don't want to use the DataGen step, have you considered using a Groovy Data Source with triple quoted strings? Here is another good page where it has a detailed example of templating with them.
