Skip to content

Unit testing should be skipped for plugins not related to changes in a pull request #1792

@westonruter

Description

@westonruter

Feature Description

When opening a pull request that changes files to one plugin, only the unit tests for that plugin should run. This will greatly speed up our workflows (and reduce wasted compute), especially now that code coverage is being performed. That said, would it be problematic if PRs didn't include coverage reports for all plugins?

Note that a PR that modifies Optimization Detective should also cause the tests for Embed Optimizer and Image Prioritizer to also run, since they are dependent on that plugin.

Naturally, all tests would run for all plugins for commits added to trunk.

This has been suggested before by @thelovekesh, but I don't remember where.

Metadata

Metadata

Assignees

No one assigned

    Labels

    InfrastructureIssues for the overall performance plugin infrastructure[Type] EnhancementA suggestion for improvement of an existing feature

    Projects

    • Status

      Not Started/Backlog 📆

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions