mongo-php-library Validation Report

Generated 2026-08-19 — SecantusDB 0.6.0b12 vs mongo-php-library 12e56461166d (vendor/mongo-php-library/).

Run uv run python -m invoke validate-php-lib to refresh. The pass rate is the analogue of the pymongo / mongo-go-driver / mongo-node-driver / mongo-java-driver / mongo-ruby-driver gauges for the official high-level PHP library — the mongodb/mongodb package Laravel + Symfony applications build on.

Summary by category

Category

Passed

Failed

Skipped

Total

Pass rate

tests/Builder

732

0

0

732

100.0%

tests/Collection

159

0

1

160

100.0%

tests/Command

53

0

0

53

100.0%

tests/Comparator

31

0

0

31

100.0%

tests/Database

70

0

0

70

100.0%

tests/Functions

0

0

4

4

tests/Model

141

1

0

142

99.3%

tests/Operation

1902

0

36

1938

100.0%

Overall

3088

1

41

3130

100.0%

Run time: 2.98s.

Failures (1)

First 30 failed cases for triage:

tests/Model :: MongoDB\Tests\Model\IndexInfoFunctionalTest::testIsText

How this is generated

mongo-php-library’s PHPUnit suite is run unmodified, against a standalone SecantusDB daemon. The submodule at vendor/mongo-php-library/ is checked out at the pinned upstream tag with zero local edits. php_lib_validation/runner.py runs composer install (one-time per checkout) to materialise PHPUnit, boots python -m secantus --storage-path <tempdir>, then runs vendor/bin/phpunit --log-junit <xml> over the curated functional directories in include_paths.py with MONGODB_URI=mongodb://127.0.0.1:<port>/ and MONGODB_DATABASE=phplib_test — the env vars tests/TestCase.php reads. The on-disk tempdir is removed after the run.

Every functional test opens a real TCP connection to the SecantusDB daemon and exchanges wire commands end-to-end, so the pass rate measures SecantusDB’s compatibility with the PHP library, not the library’s own pure-code logic. The include set is narrow on purpose: the spec-corpus suites (SpecTests / UnifiedSpecTests), GridFS, and the documentation-example tests need replica-set / transaction / CSFLE orchestration SecantusDB doesn’t provide, so they’re excluded rather than counted as environment-gated skips.