@sarthak-19 @thelovekesh Since the Performance repo is a monorepo of plugins, and since PHPUnit is going to be run separately for each plugin and thus there will be multiple coverage files, does this mean there could be multiple coverage reports? I think that would be somewhat helpful if each plugin's coverage was reported separately, although this for me is only a nice-to-have.

Yes @westonruter, that should be achievable.

Problem

I managed to run the test locally and created a coverage-report.xml, previously report was not getting generated that's why one test was failing.

But for testing purpose when I pushed the code to my draft PR, all the test is failing.

Reason

For PHP 8.1^ it's failing because PHPUnit 10 is getting used instead of 9, and for below 8.1 PHP I'm not able to understand why it's failing.

• When PHP Env is ^8.0, required PHPUnit should be 9.0^ for generating coverage report (PHPUnit ^10.0 throwing errors)
  Previously I was getting

This version of PHPUnit does not support code coverage on PHP 8
PHPUnit Version - 8.5.39
PHP Version -8.2.24

• When PHP Env. is ^7.0, then PHPUnit ^9.0 will work or not, not sure.

Questions

1. When different test case runs for different PHP versions in GH actions, how can I set PHPUnit versions for each test?
2. For generating coverage report, xdebug must be set else we'll get No coverage driver available.
   So for testing purpose I've modified package.json as --> "wp-env": "wp-env start --xdebug=develop,coverage",, But I assume this is not the correct way to do it, so how can I enable xdebug only for env where code coverage is needed.

3. I think that would be somewhat helpful if each plugin's coverage was reported separately.

When testing locally, each plugin report was getting generated but was getting replaced due to same file name, so how can I set different file name for each plugin?

cc : @westonruter @thelovekesh

• When different test case runs for different PHP versions in GH actions, how can I set PHPUnit versions for each test?

Here's how the AMP plugin configures specific PHPUnit versions:

https://github.com/ampproject/amp-wp/blob/d101379ce2044924b38834b873638547f54bcc82/.github/workflows/build-test-measure.yml#L293-L344

https://github.com/ampproject/amp-wp/blob/d101379ce2044924b38834b873638547f54bcc82/.github/workflows/build-test-measure.yml#L382-L388

https://github.com/ampproject/amp-wp/blob/d101379ce2044924b38834b873638547f54bcc82/.github/workflows/build-test-measure.yml#L398-L403

I'm not sure that's what we should do here as well.

When testing locally, each plugin report was getting generated but was getting replaced due to same file name, so how can I set different file name for each plugin?

Currently all the tests are being run together via npm run test-php:

This npm run test-php command, however, is just a shortcut for running multiple composer commands:

So I think the workflow just needs to invoke each of the plugins' test commands separately: