Skip to content

development.md

Latest commit

 

History

History
63 lines (48 loc) · 2.57 KB

development.md

File metadata and controls

63 lines (48 loc) · 2.57 KB
Raw

Development

The root composer.lock is not committed, so the first run resolves like an update.

composer update
vendor/bin/phpstan analyse
vendor/bin/phpunit --exclude-group e2e
composer cs:check
vendor/bin/bdi detect drivers && vendor/bin/phpunit --group e2e

CI runs PHPStan and the non-E2E tests on PHP 8.2/Symfony 6.4, 8.3/7.4, 8.4/8.1 and 8.5/8.1. It runs the E2E group on 8.2/6.4 and 8.5/8.1, and the style check on 8.5. To reproduce one matrix job, select the branch in the same way as the workflow. composer update on its own constrains only the packages that composer.json names, and the transitive Symfony packages then resolve to their latest branch:

composer global require symfony/flex
composer config extra.symfony.require 6.4.*
composer update

The E2E group drives Chrome against tests/Fixtures/app, which the PHP built-in web server serves.

tests/Functional/StimulusControllersMapTest.php runs StimulusBundle's own resolver over the fixture host, so on a broken host it fails with the StimulusBundle message and not with a page that does not respond. To reproduce that, remove the asset_mapper prepend from TacticMediaQaBundle::prependExtension() and run it.

The capture package and the review image have separate test commands:

cd js && npm ci && npm run build && npm test
npx playwright install chromium
QA_SCREENSHOTS_DIR=/tmp/shots npm run test:integration

From the repository root, which is the build context of the Dockerfile:

QA_SCREENSHOTS_DIR=/tmp/shots vendor/bin/phpunit --group contract
docker build -f docker/review/Dockerfile -t qa-review:local .

The contract group runs the PHP reader over a tree that the npm producer wrote. This confirms that the layout is a contract between the two producers and not the behaviour of one implementation. The group skips itself when QA_SCREENSHOTS_DIR is not set.

The Flex recipe

recipe/ contains the recipe. Neither archive contains it, and it is not published from this repository. recipe/README.md gives the target path in symfony/recipes-contrib and the reason the recipe registers dev and test.

Demo

demo/ is a complete example that you can run. It is a Symfony 8.1 application on PHP 8.4. Its single Panther journey opens each page of https://tacticmedia.com.au, captures each screen at five viewports in light and dark, and serves the review page over the captured tree. demo/playwright/ contains the same journey for Playwright and writes the same tree, so each producer gives the same six screens in the review. demo/README.md describes both producers and the container.