BLOG

Good Tests, Bad Results – How to Recognize Missing Test Data?

Why Test Data Significantly Impacts the Validity of Software Tests In many development teams, a familiar pattern emerges: a pull request is cleanly reviewed, automated tests pass, and shortly after release, issues still occur in production. This happens particularly often in systems whose data models have evolved over many years.

Read more »
BASICS

Bulk data for system and release tests

Best-Practice: Test data procurement in the context of continuous software development (PART 3/3). Before the new or modified applications go live, system, release, load or performance tests are applied. For this purpose, no fine-grained customized test case data is needed, but production-related data in larger quantities is required. These tests are

Read more »
BASICS

Customized test case data for functional, component and regression testing

Best-Practice: Test data procurement in the context of continuous software development (PART 2/3). The further development of an application usually means that different features or even bug fixes need to be implemented. Ideally, each feature gets its own environment. This environment contains only the relevant data for that particular case.

Read more »