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

Align test reporting more closely w/ status enums (as it related to "untested") #267

Open
cmcginley-splunk opened this issue Aug 27, 2024 · 0 comments

Comments

@cmcginley-splunk
Copy link
Collaborator

  • the difference between "skipped" and "untested" is not obvious to the unitiated
  • we should:
    • add a new UNSET status enum that is the default for TestResult.status (also good in that we no longer need to worry about the None type)
    • eliminate total_untested and untested_detections
    • If testing fails in an unhandled way that causes contentctl to stop altogether, then we iterate over all tests, and for any that remain UNSET after testing completes, we mark the status as ERROR with a message like TEST FAILED (ERROR): testing end state failed to be set, testing may have ended prematurely
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

No branches or pull requests

1 participant