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

Remove skip from the ResultInterpret enumeration #3269

Merged
merged 1 commit into from
Oct 10, 2024

Conversation

psss
Copy link
Collaborator

@psss psss commented Oct 8, 2024

As discussed today, the skip value was never documented in the test result key specification and was added by an accident.

There seems to be a use case to support skipping selected tests but that functionality is substantially different from the result interpretation configured by the result key which happens only after test execution is completed so most probably a new test key should be introduced for it.

Pull Request Checklist

  • implement the feature
  • modify the json schema

As discussed today, the `skip` value was never documented in the
test `result` key specification and was added by an accident.

There seems to be a use case to support skipping selected tests
but that functionality is substantially different from the result
interpretation configured by the `result` key which happens only
after test execution is completed so most probably a new test key
should be introduced for it.
@psss psss added this to the 1.38 milestone Oct 8, 2024
@psss psss added code | schema Schema used for validating config files code | trivial A simple patch - a couple of lines, an easy-to-understand change, a typo fix. area | results Related to how tmt stores and shares results labels Oct 8, 2024
@psss psss added the ci | full test Pull request is ready for the full test execution label Oct 8, 2024
@psss
Copy link
Collaborator Author

psss commented Oct 8, 2024

/packit test

@happz
Copy link
Collaborator

happz commented Oct 10, 2024

Unrelated failures, merging.

@happz happz merged commit f9642cf into main Oct 10, 2024
22 of 23 checks passed
@happz happz deleted the remove-result-interpret-skip branch October 10, 2024 07:26
The-Mule pushed a commit to The-Mule/tmt that referenced this pull request Oct 14, 2024
As discussed today, the `skip` value was never documented in the
test `result` key specification and was added by an accident.

There seems to be a use case to support skipping selected tests
but that functionality is substantially different from the result
interpretation configured by the `result` key which happens only
after test execution is completed so most probably a new test key
should be introduced for it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area | results Related to how tmt stores and shares results ci | full test Pull request is ready for the full test execution code | schema Schema used for validating config files code | trivial A simple patch - a couple of lines, an easy-to-understand change, a typo fix.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants