Test Automation
17 items tagged with "test-automation"
Best Practices9
The Test Pyramid
A testing strategy that favors many fast unit tests, fewer integration tests, and a small number of slow end-to-end tests.
The Testing Trophy
A testing model that weights integration tests most heavily, balancing static analysis, unit, integration, and end-to-end tests by confidence-per-cost.
Property-Based Testing
A technique that asserts general properties of code and lets a framework generate many randomized inputs to find counterexamples and shrink them.
Mutation Testing
A technique that injects small faults (mutants) into code and checks whether tests detect them, measuring how effective the test suite really is.
Flaky Test Management
A disciplined approach to detecting, quarantining, and fixing nondeterministic tests so CI signal stays trustworthy and developers keep merging.
Code Coverage Best Practices
Guidance on using code coverage as a signal of untested code rather than a target, including diff coverage and avoiding coverage gaming.
End-to-End Testing Best Practices
Guidance for writing reliable, maintainable end-to-end tests that exercise critical user journeys without becoming slow and flaky.
Test Data Management
Practices for provisioning realistic, isolated, and compliant test data so tests are reliable, repeatable, and free of production data exposure.
Visual Regression Testing
Automated testing that captures screenshots of UI states and compares them against baselines to detect unintended visual changes.
Anti-Patterns6
Ice-Cream Cone (Inverted Test Pyramid)
A test suite dominated by slow manual and end-to-end tests with few unit tests, making feedback slow, brittle, and expensive to maintain.
Flaky Tests
Tests that pass and fail non-deterministically without code changes, eroding trust in the suite and masking real regressions.
Assertion Roulette
A test with many unlabeled assertions, so when one fails it is unclear which condition broke or why, slowing diagnosis.
Mystery Guest
A test that depends on external data or resources not visible in the test itself, making it opaque, fragile, and non-reproducible.
Happy-Path-Only Testing
Tests that exercise only the expected, valid flow and ignore errors, edge cases, and failures — leaving real-world conditions untested.
Coverage-Driven Testing (Coverage as a Target)
Chasing a code-coverage percentage as the goal, producing tests that execute code without meaningfully asserting behavior — high numbers, low confidence.
FAQs2
What is the test pyramid?
The test pyramid is a guideline for balancing automated tests by type and quantity. Its wide base is many fast, cheap unit tests; the middle is a smal...
What is the difference between unit, integration, and end-to-end tests?
Unit tests verify a single function or class in isolation, often with dependencies mocked, and run very fast. Integration tests check that multiple co...