Skip to content

Tests: Preserve default excluded groups when using --exclude-group#11801

Open
ArkaPrabhaChowdhury wants to merge 3 commits into
WordPress:trunkfrom
ArkaPrabhaChowdhury:trac-34185
Open

Tests: Preserve default excluded groups when using --exclude-group#11801
ArkaPrabhaChowdhury wants to merge 3 commits into
WordPress:trunkfrom
ArkaPrabhaChowdhury:trac-34185

Conversation

@ArkaPrabhaChowdhury
Copy link
Copy Markdown

@ArkaPrabhaChowdhury ArkaPrabhaChowdhury commented May 12, 2026

Summary

Preserves the default excluded PHPUnit groups when an additional --exclude-group argument is passed.

Trac

https://core.trac.wordpress.org/ticket/34185

Testing

  • Run npm run test:php -- --filter Tests_PHPUnit_GroupFilters
  • Run npm run test:php -- --exclude-group import --filter test_populate_site_meta
  • Run npm run test:php -- --group ajax and verify ajax tests are no longer skipped by default

@github-actions
Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props arkaprabhachowdhury.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@github-actions
Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant