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.
More on Testing
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.
✦ Latest in Testing
Typed relationships here
Edges touching a Testing term.
- Test Doubles Leverages Anonymous Classes (PHP 7.0) Sep 10
- Mutation Testing Mitigates Goodhart's Law Sep 10
- Load Testing Contrasts with End-to-End Testing Sep 3
- Load Testing Precedes Profiling & Benchmarking Sep 2
- Load Testing Measures Tail Latency (p95, p99) Aug 22
Interfaces define the contracts that anonymous classes implement inline to construct test doubles substituting real dependencies during testing.
🤖 AI Guestbook — Testing educational data only
|
|
Last 30 days
Agents 0
No pings yet today
SEMrush 5Amazonbot 4PetalBot 4Common Crawl 2Ahrefs 2Google 1Baidu 1Bing 1
ChatGPT 1.6kGoogle 508Amazonbot 480PetalBot 373Perplexity 331SEMrush 292Ahrefs 275Scrapy 228Bing 157Unknown AI 112Claude 88Applebot 68Twitter/X 62Brave Search 39Majestic 36Meta AI 33Sogou 26Common Crawl 20Baidu 15ShapBot 7Qwen 6DuckDuckGo 3NotebookLM 2
Most referenced — Testing
No pings yet today
How they use it
crawler 4.6k
crawler_json 126
your_contextpost 10
pre-tracking 16
Category total4.8k pings
Terms pinged30 / 30
Distinct agents22
Test Parallelization Gotchas
Hidden runtime hazards when tests execute concurrently — shared state, race conditions, and resource contention turn green suites red intermittently.
5mo ago
Testing intermediate
Test Doubles
PHP 8.0+
1
Substitute objects used in tests to replace real dependencies — mocks, stubs, spies, fakes, and dummies each serve a different purpose.
7mo ago
Testing intermediate
Naming Test Methods (Given/When/Then)
4
Test method names should describe behaviour, not implementation — test_calculateTotal_givenDiscountedItems_returnsReducedPrice beats test_calculateTotal().
7mo ago
Testing beginner
Test-Driven Development (TDD)
PHP 7.0+
2
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).
7mo ago
Testing intermediate
Fuzz Testing
PHP 7.0+
Automatically generating random, unexpected, or malformed inputs to find crashes, assertion failures, and security vulnerabilities that manual test cases miss.
7mo ago
Testing advanced
Parameterised / Data-Driven Tests
PHP 5.0+
Running the same test logic with multiple input/output pairs — PHPUnit's @dataProvider eliminates copy-pasted test methods for the same behaviour with different values.
7mo 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.
7mo 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.
7mo ago
Testing intermediate
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.
7mo ago
Testing beginner
Visual Regression Testing
Automatically comparing screenshots of UI components or pages to a baseline — catching unintended visual changes that functional tests miss.
7mo ago
Testing intermediate
Acceptance Testing / BDD (Behat)
PHP 5.0+
3
Testing that the system meets business requirements from a user perspective — written in plain language (Gherkin) and automated with Behat in PHP.
7mo ago
Testing intermediate
Behaviour-Driven Development (BDD)
PHP 5.0+
2
A development practice where tests are written in business-readable language (Given/When/Then) that domain experts, developers, and testers all understand.
7mo ago
Testing intermediate
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.
7mo ago
Testing beginner
Consumer-Driven Contract Testing
1
A testing approach where the consumer of an API defines a contract of what it expects, and the provider verifies it satisfies that contract — enabling independent deployment of microservices.
7mo ago
Testing advanced
End-to-End Testing
3
Testing complete user flows through a real browser against a running application — verifying that all layers work together from UI to database.
7mo ago
Testing intermediate
Flaky Tests
Tests that pass and fail non-deterministically on the same code — caused by shared state, timing dependencies, external services, or random data.
7mo ago
Testing intermediate
Integration Testing
PHP 5.0+
3
Tests that verify multiple components work correctly together — often involving real databases, HTTP clients, or third-party services.
7mo ago
Testing intermediate
Load Testing
PHP 5.0+
3
Testing system behaviour under expected and peak load conditions to identify performance bottlenecks and breaking points before they affect users.
7mo ago
Testing intermediate
Mocking Best Practices (PHPUnit & Mockery)
PHP 5.0+ Guidelines for effective mocking: mock interfaces not classes, avoid over-mocking, prefer stubs for queries and mocks for commands.
7mo ago
Testing intermediate
Mutation Testing
PHP 7.1+
1
A technique that automatically modifies source code and checks whether tests fail — surviving mutations indicate test gaps even where line coverage appears complete.
7mo ago
Testing advanced