In this session we will show you different ways of how to get your test data setup efficiently and effectively. We will identify what to test, and how to isolate it, thus making it less database dependent or maybe no dependency at all.

An often heard complaint from teams starting with test automation, is the vast extend of data setup. Seemingly a whole database needs to get setup before any action under test can be executed. This often holds back whole development teams to start their test automation effort. Or, once started, makes some wonder whether they should continue this effort as it appears to be too costly, both in maintenance and repeated execution.

Moreover, you will see how these choices highly correlate to the structure of your production code and we will unveil choices you can make in the future regarding your code structure.