Testing terms
The discipline that lets you change code without fear
Tests are the safety net that lets you refactor without fear and ship without dread. This category covers unit, integration, and end-to-end testing strategies, test doubles, coverage metrics, TDD and BDD approaches, and the tooling ecosystem across languages. A well-tested codebase is not slower to build — it is faster to evolve.
Naming Test Methods (Given/When/Then)
Test method names should describe behaviour, not implementation — test_calculateTotal_givenDiscountedItems_returnsReducedPrice beats test_calculateTotal().
2mo ago
testing beginner
Test Naming Conventions
Well-named tests read as specifications — they document what the system does, make failure messages self-explanatory, and allow filtering tests by feature or scenario.
2mo ago
testing beginner
Code Coverage PHP 5.0+ A metric measuring the percentage of code executed by a test suite — useful for identifying untested paths, not a quality guarantee.
2mo ago
testing beginner
Regression Testing
Re-running existing tests after code changes to verify that previously working functionality has not been broken — the primary safety net for continuous delivery.
2mo ago
testing beginner
Smoke Testing
A minimal set of tests run immediately after deployment to verify the application is alive and its critical paths are functional before deeper testing or traffic.
2mo ago
testing beginner
Test Pyramid PHP 5.0+ A model advocating many fast unit tests at the base, fewer integration tests in the middle, and a small number of slow E2E tests at the top.
2mo ago
testing beginner
Unit Testing PHP 5.0+
Automated tests that verify individual units of code (classes, methods) in isolation from external dependencies.
2mo ago
testing beginner