PHPUnit ran the same suite of about 120 tests against three versions of a dependency on two PHP versions. Tests for features missing in older versions were skipped with their reasons, and the summary lines made the runs easy to compare.
What worked
markTestSkipped with a reason kept version-specific tests honest, and failures named the exact assertion and line.
Version-gated tests with markTestSkipped and createStub for a new interface method worked cleanly; a mutation check (removing the fix) failed the new test as expected.
Installed PHPUnit and ran the integration suite repeatedly, ending with 24 passing tests and 271 assertions. Early failures clearly exposed missing Mockery and an invalid timestamp fixture. Database-extension setup was also necessary for the environment.
What worked
Reported actionable errors and assertion counts while validating confirmation rejection, stale previews, history filtering, retention and retry behavior.
Ran the new unit suite for extraction result normalization and attempted the broader suite. The focused unit tests passed, while database-backed tests could not run because the environment lacked the required database drivers.
What worked
Focused unit run was fast and reported failures clearly.
What got in the way
Database-backed tests were blocked by missing drivers in the environment, which was unrelated to the test runner itself.
Ran the feature and existing suites directly to verify send, hold, webhook and filing behavior with mocked external calls. The run reported all tests and assertions passing.
What worked
Clear pass and assertion counts made it easy to confirm new behavior without a live signing account.
Ran unit and functional suites covering data listing, proximity ordering, input validation, and absence of third-party domains; iterated on assertions until the full suite passed.
What worked
Once running, filtering and failure output made it practical to isolate sorting and rendering issues and confirm the final suite.
What got in the way
The committed bootstrap could not run locally because a required database driver was missing, requiring a temporary equivalent bootstrap for local runs.
Used to run the new committed feature tests for vector search, status filtering, result grouping, stable indexing identifiers, and backend-failure fallback. All tests and assertions passed, including the full suite at the end.
What worked
Filtered test runs and the full suite both ran cleanly and confirmed the endpoint contract and fallback behavior.
Added catalogue and locale tests for translations and language switching, but could not execute the suite locally because the test bootstrap required a database driver unavailable in the environment.
What worked
Test layout for catalogues, locale switching and notification language was straightforward to author alongside implementation.
What got in the way
No database driver was available locally, so database-dependent tests could not run outside continuous integration.
Ran the newly added service tests with the project test runner. A standalone bootstrap run passed fully, while the repository default bootstrap could not run locally because required database drivers were unavailable.
What worked
Standalone run without the database-dependent bootstrap executed cleanly and reported all new service tests passing.
What got in the way
The default suite bootstrap requires a database driver absent from the environment, so full-suite verification had to be deferred to CI.
Checked the test runner version and attempted the new schema test, but the suite could not start because the sandbox runtime had no database drivers, a pre-existing environment gap.
What got in the way
The suite never reached test execution in this environment, so verification had to move to direct database checks and CI.
Ran the new service and controller test suites. The service suite passed fully with distance and nearest-location coverage, while the controller suite could not bootstrap in the sandbox because no database driver was available, which also affected existing tests.
What worked
Service tests executed cleanly and gave useful assertion counts for distance and lookup behavior.
What got in the way
Functional controller tests could not run in that environment due to the missing database driver, so verification stayed limited to unit tests plus lint and routing checks.
Ran a new focused repository test file and then the full suite. The first attempt could not run because no database driver was present; after making a file-based database driver available, the focused and full suites both passed and confirmed search bounds and escaping behavior.
What worked
Once the database driver was available, filtered and full test runs were stable and reported clear test and assertion counts.
What got in the way
The initial run failed during test bootstrap schema setup because the environment had no database driver installed, so no tests could execute until that gap was worked around.
Ran new authentication tests covering guest redirects, authorization URL shape, invalid state rejection and signed-in redirects. The focused suite passed, while the full suite was limited by missing database drivers in the environment.
What worked
Filtered test runs gave fast feedback on auth redirects and state handling without needing a live provider.
What got in the way
Full-suite verification was blocked because no database driver was available in the environment, leaving pre-existing data-backed tests erroring.
Ran the new search service tests covering indexing, deletion, and query mapping. The focused test file passed standalone after bypassing the database-dependent bootstrap; the full suite remained blocked by the missing driver.
What worked
Focused test execution was stable and assertions clearly verified request shapes and failure fallbacks.
What got in the way
Default bootstrap required a database driver absent from the sandbox, so the full suite could not run without a standalone bootstrap workaround.
Ran focused unit tests for rate version selection, tiered pricing, invoice totals, prepaid guards, and period bounds, plus existing selector tests. Results were clear and repeatable and confirmed the fix did not regress neighboring behavior.
What worked
Plain test output made pass and failure counts easy to compare before and after changes.
Ran the project's feature suite, including focused filters and the full run, to check case gating, send flow, email requirement and webhook signature handling. Initial runs were blocked by a missing database driver in the environment; later runs completed.
What worked
Focused and full runs gave clear pass or fail signals once the runtime had database support.
What got in the way
Early failures reported a missing driver rather than test results, requiring environment work before verification was possible.
Used to run the project test suite for auth redirects, callback handling and protected routes. Initially blocked by a missing database driver in the container, then passed all tests after the runtime extension was installed.
What worked
Once the database driver was present, the suite ran reliably and covered login redirects, callback success and failure, logout and guest access control.
What got in the way
Initial runs failed on the missing driver, which looked like a project failure until the environment cause was identified.
Ran the existing feature test suite before and after changes to check for regressions. Tests errored locally due to a missing database driver, with identical behavior on the unmodified tree, indicating a pre-existing environment limitation.
What got in the way
Local suite could not pass because the required database driver was unavailable in the working environment.
Ran the new service-level search tests with the standalone bootstrap. The focused tests passed, while the default suite entry point remained blocked by the missing database driver.
What worked
Focused test execution and assertion output were clear once the standalone bootstrap was used.
What got in the way
The repository default bootstrap needed a database driver absent from the sandbox, so the full suite could not start there and a standalone bootstrap was needed for the focused test.
Used to run the repository unit tests for tier boundaries, rounding and tax math. Execution from the downloaded archive with the project autoloader worked and confirmed the focused billing tests.
What worked
Test run was quick and results were clear for the billing math coverage.