How to write tests that need a lot of data?

In this talk Sander explains how you can write unit and integration tests that need a lot of data. As an example Sander shows how to test code of a warehouse management system (WMS). This is not about big-data, though.


Does your production code need a lot of data? How do you setup this data for your unit and integration tests? Do you fill a database with a fixed set of data that is to be used by all tests? What if for a new use case you need more data?
And how many mocks do you use in your unit tests? Do you have to add more mocks for each use case that you implement?
Visit Sander's talk about how to write tests that need a lot of data. We are not talking about big-data, but about combining data from several tables of database to implement a use case. How can you write test code that is easy to read and easy to maintain?
Sander shows examples of code for a warehouse management system (WMS) and explains how complex the production code is. Then he shows how the tests for the production code can be implemented and how to set up the test data.


Abstract as a tweet:

In this talk Sander explains how to write tests that need a lot of data using code of a warehouse management system as example.

Python Skill Level:

basic

Domains:

Algorithms, Code-Review

Domain Expertise:

some