Skip to content

Migrate PHPUnit configs and homogenize them #2867

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 27, 2025

Conversation

Kocal
Copy link
Member

@Kocal Kocal commented Jun 25, 2025

Q A
Bug fix? no
New feature? no
Docs? no
Issues Fix #...
License MIT

To get rid of:

Warning:       Your XML configuration validates against a deprecated schema.
Suggestion:    Migrate your XML configuration using "--migrate-configuration"!

@carsonbot carsonbot added the Status: Needs Review Needs to be reviewed label Jun 25, 2025
@carsonbot carsonbot added Status: Reviewed Has been reviewed by a maintainer and removed Status: Needs Review Needs to be reviewed labels Jun 26, 2025
@Kocal Kocal force-pushed the migrate-phpunit-config branch 2 times, most recently from 95b7e78 to 97e4215 Compare June 27, 2025 04:14
@Kocal
Copy link
Member Author

Kocal commented Jun 27, 2025

I'm removing the executionOrder="random", weird things are happening on LiveComponent tests Cannot find a match for template "...". Cache may be corrupt:

Testing 
...............................................................  63 / 273 ( 23%)
..................F....F....................................... 126 / 273 ( 46%)
............................................................... 189 / 273 ( 69%)
............................................................... 252 / 273 ( 92%)
.....................                                           273 / 273 (100%)

Time: 00:42.025, Memory: 98.50 MB

There were 2 failures:

1) Symfony\UX\LiveComponent\Tests\Functional\EventListener\LiveComponentSubscriberTest::testItUseBlocksFromEmbeddedContextUsingMultipleComponentsWithNamespacedTemplate
Expected successful status code (2xx) but got 500.

/home/runner/work/ux/ux/src/LiveComponent/vendor/zenstruck/assert/src/Assert/Handler/PHPUnitHandler.php:36
/home/runner/work/ux/ux/src/LiveComponent/vendor/zenstruck/assert/src/Assert.php:45
/home/runner/work/ux/ux/src/LiveComponent/vendor/zenstruck/assert/src/Assert.php:65
/home/runner/work/ux/ux/src/LiveComponent/vendor/zenstruck/browser/src/Browser/KernelBrowser.php:411
/home/runner/work/ux/ux/src/LiveComponent/tests/Functional/EventListener/LiveComponentSubscriberTest.php:293

2) Symfony\UX\LiveComponent\Tests\Functional\EventListener\LiveComponentSubscriberTest::testItUseBlocksFromEmbeddedContextUsingMultipleComponents
Expected successful status code (2xx) but got 500.

/home/runner/work/ux/ux/src/LiveComponent/vendor/zenstruck/assert/src/Assert/Handler/PHPUnitHandler.php:36
/home/runner/work/ux/ux/src/LiveComponent/vendor/zenstruck/assert/src/Assert.php:45
/home/runner/work/ux/ux/src/LiveComponent/vendor/zenstruck/assert/src/Assert.php:65
/home/runner/work/ux/ux/src/LiveComponent/vendor/zenstruck/browser/src/Browser/KernelBrowser.php:411
/home/runner/work/ux/ux/src/LiveComponent/tests/Functional/EventListener/LiveComponentSubscriberTest.php:261

@Kocal Kocal force-pushed the migrate-phpunit-config branch from 600748d to 061c314 Compare June 27, 2025 08:54
@Kocal Kocal changed the title Migrate and improve PHPUnit configs Migrate PHPUnit configs and homogenize them Jun 27, 2025
@Kocal Kocal force-pushed the migrate-phpunit-config branch from 061c314 to dfd4fe1 Compare June 27, 2025 09:05
@Kocal
Copy link
Member Author

Kocal commented Jun 27, 2025

I removed some of last commits, and instead only focused on the PHPUnit configs migrations but also homogenization (with what https://github.com/symfony/symfony does).

@Kocal Kocal merged commit 18baea3 into symfony:2.x Jun 27, 2025
23 of 31 checks passed
@Kocal Kocal deleted the migrate-phpunit-config branch June 27, 2025 09:15
Kocal added a commit that referenced this pull request Jun 27, 2025
This PR was merged into the 2.x branch.

Discussion
----------

[Translator][Tests] Minor fixes in tests context

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->
| Docs?         | no <!-- required for new features -->
| Issues        | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License       | MIT

<!--
Replace this notice by a description of your feature/bugfix.
This will help reviewers and should be a good start for the documentation.

Additionally (see https://symfony.com/releases):
 - Always add tests and ensure they pass.
 - For new features, provide some code snippets to help understand usage.
 - Features and deprecations must be submitted against branch main.
 - Update/add documentation as required (we can help!)
 - Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry
 - Never break backward compatibility (see https://symfony.com/bc).
-->

Cherry-picked from #2867, the following fixes only apply inside tests context, it does not have impact in real-life scenarios:
1. The static variable `$alreadyGenerated` now becomes a private property `alreadyGeneratedConstants. When tests were executed randomly in #2867, it was impossible to assert on generated translations files because constants names were kept in static cache even when the class `TranslationsDumper` was initialized for each test.
2. `self::$cacheDir` is a directory, so using `rmdir` is the best way to go instead of `unlink`

Commits
-------

6e58d54 [Translator] Move already generated constants from static var to class property
Kocal added a commit that referenced this pull request Jun 28, 2025
This PR was squashed before being merged into the 2.x branch.

Discussion
----------

[Tests] Fix functional tests Turbo

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->
| Docs?         | no <!-- required for new features -->
| Issues        | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License       | MIT

Maybe I went to quick on #2867, maybe using `<server>` instead of `<env>` matters...

**EDIT:** it seems that Turbo functional tests were broken since few weeks / months now, because of Chrome 137, see symfony/panther#675.

Passing `PANTHER_DEVTOOLS=0` worked like a charm.

Commits
-------

9b42f13 [Tests] Fix functional tests Turbo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Reviewed Has been reviewed by a maintainer
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants