CodeClarityLab / Glossary
Ctrl K
← Home ← Codex ← DEBT
Browse by Category
+ added · ✎ updated 7d
⚖ Terms of Use ✉ Contact

Testing terms

9 terms of 1487 total

🧪 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.

More on Testing history · 5 references · key concepts

History

Software testing emerged informally alongside early programming in the 1950s–60s, when developers manually verified output against expected results. The discipline formalized in the 1970s–80s as structured methodologies like unit testing and integration testing became standard practice, driven by the need to manage complexity in larger systems. The 1990s–2000s saw the rise of automated testing frameworks (JUnit in Java, xUnit derivatives) and test-driven development (TDD), popularized by Kent Beck and the agile movement, which shifted testing leftward in the development cycle. The 2010s brought broader adoption of continuous integration/continuous deployment (CI/CD) pipelines, property-based testing, and contract testing, alongside formalization of the test pyramid and testing matrix concepts. Today, testing spans unit, integration, end-to-end, and specialty domains (performance, security, visual regression), with modern teams treating test infrastructure as a first-class concern and using mutation testing and snapshot techniques to validate test quality itself.

Key concepts

  • Unit Testing
  • Test Naming Conventions
  • Test Fixtures & setUp() Best Practices
  • Test Isolation Strategies
  • Test-Driven Development (TDD)
  • Integration Testing
  • Test Pyramid
  • Code Coverage

Best references

  • Test Driven Development: By Example Kent Beck's foundational book covering TDD principles, test-first workflows, and practical patterns. Essential reference for understanding TDD methodology and its application across languages including PHP.
  • PHPUnit Documentation Official reference for PHP's de facto unit testing framework. Covers assertions, test doubles, fixtures, data providers, and test isolation—directly applicable to PHP testing practices.
  • The Test Pyramid Martin Fowler's widely-cited article defining the test pyramid concept (unit, integration, end-to-end). Provides strategic framework for balancing test types and costs.
  • Consumer-Driven Contracts and PACT Official Pact Foundation documentation for contract testing methodology. Authoritative source for consumer-driven contract testing patterns and cross-language tooling.
  • Behavior-Driven Development (BDD) and Behat Official Behat documentation implementing BDD for PHP. Covers Gherkin syntax, acceptance testing, and behavior-driven development practices with concrete PHP examples.
🧠 Logic graph · Testing
11 edges here
5 verbs used
14 terms touched
✦ Latest in Testing

Typed relationships here

Edges touching a Testing term.

Sort A → Z Recently Added Recently Updated Difficulty Most Viewed Most Rated Most Shared
Level All Beginner Intermediate Advanced
✕ Clear A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Test Parallelization Gotchas
Hidden runtime hazards when tests execute concurrently — shared state, race conditions, and resource contention turn green suites red intermittently.
3w ago testing intermediate
Test Doubles PHP 8.0+ 🧠 2
Substitute objects used in tests to replace real dependencies — mocks, stubs, spies, fakes, and dummies each serve a different purpose.
2mo ago testing intermediate
Test-Driven Development (TDD) PHP 7.0+ 🧠 1
A development practice where tests are written before the code they test — Red (write a failing test), Green (write the minimum code to pass), Refactor (improve without breaking tests).
3mo ago testing intermediate
Test Coverage Types PHP 7.0+
Line coverage (lines executed), branch coverage (if/else paths), mutation testing (do tests detect actual bugs) — each measures a different aspect of test quality.
3mo ago testing intermediate
Test Environment Parity
Dev, staging, and production must use identical PHP versions, MySQL versions, and OS configurations — divergence causes bugs that only appear in production.
3mo ago testing intermediate
Test Data Builders PHP 7.0+
A pattern for constructing test objects with sensible defaults that can be selectively overridden — reducing test setup noise and making the relevant data explicit.
3mo ago testing intermediate
Test Fixtures & setUp() Best Practices
Managing test state with setUp()/tearDown(), object mothers, and factories — keeping tests isolated, readable, and fast.
3mo ago testing intermediate
Test Isolation Strategies PHP 7.0+
Ensuring each test starts from a known clean state — using database transactions, in-memory fakes, or container resets so tests don't bleed state into each other.
3mo ago testing intermediate
Diagram: Test-Driven Development (TDD) Test-Driven Development (TDD) PHP 5.0+
A development practice where tests are written before production code, driving design through the Red-Green-Refactor cycle.
3mo ago testing intermediate
✓ schema.org compliant