@@ -429,6 +429,68 @@ After the `Psalm phar is installed`_, the analysis can be run locally with:
429
429
430
430
$ psalm.phar src/Symfony/Component/Workflow
431
431
432
+ Automated Tests
433
+ ~~~~~~~~~~~~~~~
434
+
435
+ A series of automated tests will run when submitting the pull request.
436
+ These test the code under different conditions, to be sure nothing
437
+ important is broken. Test failures can be unrelated to your changes. If you
438
+ think this is the case, you can check if the target branch has the same
439
+ errors and leave a comment on your PR.
440
+
441
+ Otherwise, the test failure might be caused by your changes. The following
442
+ test scenarios run on each change:
443
+
444
+ ``PHPUnit / Tests ``
445
+ This job runs on Ubuntu using multiple PHP versions (each in their
446
+ own job). These jobs run the testsuite just like you would do locally.
447
+
448
+ A failure in these jobs often indicates a bug in the code.
449
+
450
+ ``PHPUnit / Tests (high-deps) ``
451
+ This job checks each package (bridge, bundle or component) in ``src/ ``
452
+ individually by calling ``composer update `` and ``phpunit `` from inside
453
+ each package.
454
+
455
+ A failure in this job often indicates a missing package in the
456
+ ``composer.json `` of the failing package (e.g.
457
+ ``src/Symfony/Bundle/FrameworkBundle/composer.json ``).
458
+
459
+ This job also runs relevant packages using a "flipped" test (indicated
460
+ by a ``^ `` suffix in the package name). These tests checkout the
461
+ previous major release (e.g. ``4.4 `` for a pull requests on ``5.4 ``)
462
+ and run the tests with your branch as dependency.
463
+
464
+ A failure in these flipped tests indicate a backwards compatibility
465
+ break in your changes.
466
+
467
+ ``PHPUnit / Tests (low-deps) ``
468
+ This job also checks each package individually, but then uses
469
+ ``composer update --prefer-lowest `` before running the tests.
470
+
471
+ A failure in this job often indicates a wrong version range or a
472
+ missing package in the ``composer.json `` of the failing package.
473
+
474
+ ``continuous-integration/appveyor/pr ``
475
+ This job runs on Windows using the x86 architecture and the lowest
476
+ supported PHP version. All tests first run without extra PHP
477
+ extensions. Then, all skipped tests are run using all required PHP
478
+ extensions.
479
+
480
+ A failure in this job often indicate that your changes do not support
481
+ Windows, x86 or PHP with minimal extensions.
482
+
483
+ ``Integration / Tests ``
484
+ Integration tests require other services (e.g. Redis or RabbitMQ) to
485
+ run. This job only runs the tests in the ``integration `` PHPUnit group.
486
+
487
+ A failure in this job indicates a bug in the communication with these
488
+ services.
489
+
490
+ ``PHPUnit / Tests (experimental) ``
491
+ This job always passes (even with failing tests) and is used by the
492
+ core team to prepare for the upcoming PHP versions.
493
+
432
494
.. _rework-your-patch :
433
495
434
496
Rework your Pull Request
0 commit comments