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

OPCT-226: Introduce knowledge document for OPCT Report Rules #77

Merged
merged 2 commits into from
Aug 24, 2023

Conversation

mtulio
Copy link
Contributor

@mtulio mtulio commented Aug 23, 2023

This change introduces the document used in the report enhancement in progress at #76

The Rules are a set of tests with fixed acceptance criteria that will evaluate the data collected when running report command. To allow flexibility and increase the UX, we are only keeping in the code the "Rule ID", linking it to a "Knowledge Base" to explore why the rule is failing, and the recommended next steps.

The version of #76 is tested internally by developers but the document can be available as a dev preview when the report frontend is mounting the hyperlinks for the Rules.

The demo is available here (direct 4:40) [Red Hat only]: https://drive.google.com/file/d/1v4EIO1mXesDKKy0meZeiVcZ-kSjf7o_E/view?usp=sharing

The rules are implemented here: https://github.com/redhat-openshift-ecosystem/provider-certification-tool/blob/87d4f19f7454ed388d546b0737f7462a6235189f/internal/pkg/summary/checks.go

This is how it will be referenced in CLI:
./opct-dev report results-failed-registry.tar.gz --save-to /tmp/results/ --loglevel debug
Screenshot from 2023-08-23 16-12-42

This is how it will be linked in the HTML report:

Screenshot from 2023-08-23 16-15-36

Screenshot from 2023-08-23 16-17-17

@mtulio mtulio added the kind/documentation Categorizes issue or PR as related to documentation. label Aug 23, 2023
@mtulio mtulio changed the title doc/review: minimal version of OPCT Rules OPCT-226: doc/review - minimal version of OPCT Report Rules Aug 23, 2023
@mtulio mtulio changed the title OPCT-226: doc/review - minimal version of OPCT Report Rules OPCT-226: Introduce knowledge document for OPCT Report Rules Aug 23, 2023
@mtulio mtulio added kind/feature Categorizes issue or PR as related to a new feature. kind/dev-preview labels Aug 23, 2023
@mtulio mtulio added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Aug 23, 2023
mtulio added a commit to mtulio/provider-certification-tool that referenced this pull request Aug 23, 2023
@rvanderp3
Copy link
Contributor

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 24, 2023
@openshift-ci
Copy link

openshift-ci bot commented Aug 24, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rvanderp3

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 24, 2023
@rvanderp3 rvanderp3 merged commit c3b7f72 into redhat-openshift-ecosystem:main Aug 24, 2023
5 checks passed
@faermanj
Copy link
Contributor

/lgtm
/approve

Copy link
Contributor

@faermanj faermanj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@mtulio mtulio deleted the doc-report-rules branch August 24, 2023 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/dev-preview kind/documentation Categorizes issue or PR as related to documentation. kind/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants