What actually makes a test flaky?
Why an error and a failure are different test results, and why that matters when you call a test flaky.
Why an error and a failure are different test results, and why that matters when you call a test flaky.
Five mistakes I kept making with integration tests, from writing too many to leaving artifacts behind.
Why NUnit’s constraint assertion model gives you better failure messages than the classic model.
Pair NUnit’s TestCaseData with TestCaseSource to move setup out of your tests and document each case.
Use a .runsettings file and TestContext.Parameters to pass configuration into NUnit integration tests without config-file templating.
A closer look at TestContext.CurrentContext in NUnit: the current test, its result, working directories and the Randomizer.
A tour of NUnit’s TestContext static properties and methods: output, errors, progress, parameters, formatters and attachments.
Write and run your first NUnit unit test in C#, from installing the packages to reading the results.
Fourteen books on software testing I picked to build my testing library, and why two of them went to the top.