Skip to content
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

Feature Request: Add "regression" option to fail_on parameter #624

Open
Alexgar24 opened this issue Sep 27, 2024 · 0 comments
Open

Feature Request: Add "regression" option to fail_on parameter #624

Alexgar24 opened this issue Sep 27, 2024 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@Alexgar24
Copy link

Hello,

Thank you for developing the publish-unit-test-result-action; it's greatly enhancing our CI workflows.

Feature Request:

Please add a "regression" option to the fail_on parameter.

Use Case:

In our project, some tests are currently failing, and we're working on fixing them. We want the action to fail only if new test failures are introduced compared to the previous commit. This helps us catch regressions without being hindered by existing failures.

Note:

Since the action already compares test results with the parent commit to display changes in the summary, implementing this feature might be straightforward.

Example Usage:

- name: Publish Unit Test Results
  uses: EnricoMi/publish-unit-test-result-action@v2
  with:
    files: '**/test-results.xml'
    fail_on: 'regression'

Expected Behavior:

The action fails the workflow if the number of test failures or errors has increased compared to the parent commit.
If the number of failures has decreased or remained the same, the workflow passes.
Thank you for considering this feature!

Best regards,

Álex

@EnricoMi EnricoMi added enhancement New feature or request good first issue Good for newcomers labels Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

2 participants