If you write code to SQL Server then you might be interested in this: I have written a tSQLt tdd training course which has helped over 500 people learn both tSQLt and how to apply TDD practices to their SQL Server T-SQL development, you can join the course at https://courses.agilesql.club.

Validating upstream data quality in ETL processes, SQL edition

It is a non-null constraint, not a non-ish-null constraint You are writing an ETL process, part of t...

How do test the upstream data is good in an etl process (etl testing part 3)?

In the first two parts of this series (https://the.agilesql.club/2019/07/how-do-we-test-etl-pipeline...

How do we prove our ETL processes are correct? How do we make sure upstream changes don't break our processes and break our beautiful data?

ETL Testing Part 2 - Operational Data Testing This is the second part of a series on ETL testing, th...

How do we test ETL pipelines? Part one unit tests

Why do we bother testing? Testing isn’t an easy thing to define, we all know we should do it, when s...

How to load test a SQL database

How do you know whether a database code change is going to be great, okay or awful? If you want to t...

Database testing and ETL processes

Unit testing using tSQLt is really great, you call FakeTable on any tables your code touches and the...