From add on the fly, to using random data to saving seed data in DB (Link to the story in first comment)<\/p>\n

After using seed data which resides in a baseline DB and restoring it when needed,<\/p>\n

Now we’ve moved on to the next problem:<\/p>\n

How to add data to ‘Six’ baselines, that’s right, one test which has to run on 6 different environments needs the same seed data<\/p>\n

We have been adding seed data manually, but for 6 it’s not going to be easy<\/p>\n

Since it does not have to be created just 6 times, but every time before we create the seed data on baseline, we test it by creating on the ‘restoring’ DB,<\/p>\n

So the number jumps to ’12’ times<\/p>\n

The few options we talked about to help with this:
\n– Use UI scripts to create seed data (for data which is simple)
\n– Improve the API automation and use it to create seed data, just like UI above
\n– Finally (which I don’t want to do AT ALL), create data to the DB directly<\/p>\n

The last option has many problems, schema across versions is not the same, data creation is not the same, existing data might not be exactly same either..<\/p>\n

The brainstorming is going on, but an interesting challenge to have.<\/p>\n

Thoughts?<\/p>\n

#QsDaily #Automation #testdata<\/p>\n<\/div>