A guide on introducing Test-Driven Development (TDD) to a software team through leading by example and building consensus.
A developer investigates a bug in a Space War game where duplicate bases cause crashes, detailing the debugging process and unit testing.
A discussion on analyzing confusing Gherkin scenarios in software testing, focusing on understanding domain intent before rewriting.
Learn how to write automated tests for your Django project to verify functionality and save time on manual checks.
A guide to diagnosing and fixing slow CI/CD pipelines, focusing on reducing lead time to under 15 minutes with anti-patterns and optimization strategies.
A software developer draws parallels between scientific experiments and software development, discussing how unexpected test results and failures can be valuable learning opportunities.
Explores using resilient randomized tests to improve software system robustness and prevent regressions during maintenance and change.
A discussion on why there's no single correct way to write tests, challenging the dogma around unit testing and TDD.
A practical guide to Test-Driven Development (TDD), explaining the red-green-refactor cycle and when it's most beneficial to use.
Explains the importance of frontend testing for user experience, team confidence, and preventing production bugs in non-trivial applications.
Argues against clearing the database between automated tests, citing speed, correctness, and parallelism benefits.
A survey analysis on how the practice of Specification by Example has evolved over the decade since the author's book, focusing on its impact on product quality.
Explains why you should make your tests fail to ensure they are actually testing the intended functionality and not giving false confidence.
A software testing professional reflects on keynoting at Selenium Conference seven years after first attending, discussing the evolution of test automation.
Introduces the S.A.C.R.E.D mnemonic for creating stable, deterministic automated software tests, covering state, actions, assertions, reporting, execution, and determinism.
A reflective article exploring the philosophical and practical challenges of preventing software bugs, questioning what 'prevention' truly means.
A look at the current state and future predictions for test automation, including trends like multi-layer testing and self-healing tools.
A guide on shifting testing focus from code coverage to use case coverage to build confidence in applications.
A psychology graduate turned QA team lead shares how psychological principles like understanding user motivation improve software testing.
Argues that code coverage is a flawed metric for software quality, comparing it to IQ tests, and demonstrates its limitations with examples.
