Skip to content
SESAME
Menu

Proof#

The name does double duty: this is where SESAME proves itself. There are two kinds of proof, the private proof site that exercises the library against real Wayne State applications, and the test suite anyone can run locally.

Last run#

Check Date Commit Result Duration
Test suite (PHPUnit) on PHP 8.3.36 2026-11-11 85bdbf0 pass, 926 tests, 3075 assertions 3.6 s
Test suite (PHPUnit) on PHP 8.4.27 2026-11-11 85bdbf0 pass, 926 tests, 3075 assertions 3.2 s
Test suite (PHPUnit) on PHP 8.5.12 2026-11-11 85bdbf0 pass, 926 tests, 3075 assertions 3.3 s
composer ci, the whole gate (validate, tests, Pint, PHPStan, agent-ready check, docs check, audit), Composer 2.11.1 on PHP 8.5.12 2026-11-11 85bdbf0 pass, all seven steps (tests: 926, 3075 assertions; PHPStan: no errors; audit: no advisories) 12 s, after a composer install from a warm cache

The run is on the Unreleased work after 0.7.4: php artisan sesame:check, its front-page bench, and the SameSite=Strict warning in NativeSession. The commit that records it changes this page and its built copy only. The durations are from Docker Desktop on Windows with the repo copied into a Docker volume, so file access is fast. To refresh it, rerun the Docker commands further down on the commit you want to record and update this table with the new date, sha and results. The private proof site was not run here: it needs a Wayne State employee sign-in and the real services.

The proof site#

Proof runs against real Wayne State applications on a private site, proof.apps.wayne.edu/sesame, behind a Wayne State employee sign-in. It is the place to check the library end to end, against the real services, before anything ships.

Tests#

Maintainers: how to build, test and release this project, and where its data comes from, is in MAINTAINING.md.

No PHP on the machine? Fine. Docker runs the suite:

docker run --rm -v "${PWD}:/app" -v stack-composer-cache:/tmp/cache -w /app composer:2 composer install --no-interaction
docker run --rm -v "${PWD}:/app" -w /app php:8.3-cli vendor/bin/phpunit
docker run --rm -v "${PWD}:/app" -w /app php:8.4-cli vendor/bin/phpunit
docker run --rm -v "${PWD}:/app" -w /app php:8.5-cli vendor/bin/phpunit

Static analysis is PHPStan at level 8 from Pinstripe's strict preset (vendor/waynestate/pinstripe/phpstan/strict.neon, included through the waynestate/pinstripe dev dependency): strict rules stay on, and a call to a deprecated method fails the build. composer ci runs the whole gate, validate through tests, Pint and PHPStan:

docker run --rm -v "${PWD}:/app" -v stack-composer-cache:/tmp/cache -w /app composer:2 composer ci