What is the best way to customize data to automate ATDD styles?

Question

I assume that in most implementations there is a basic set of known data that revitalizes every test run every time. I think that there are several main schools of thought.

• Enter test code, use application calls to create data.
• If the test code expands the data manually using direct calls to the data warehouse.
• This basic dataset has everything you need to run tests.

I think it’s obvious that No. 3 is the least supported approach. But I'm still wondering if anyone has dealt with this. Perhaps you can have databases for various scenarios, and you can add them from the test code.

Answer 1

It depends on the type of data and your domain. I had an unsuccessful attempt when the circuit was not yet stable. We were constantly having problems adding data to new and changed columns, which all the time analyzed all the tests.

Now we successfully use the initial state data in which the data set will be largely fixed, stable circuits and is required in the same state for all tests. (e.g. zip code database)

for most other materials, tests are responsible for setting up the data itself. It works for us!