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

e2e: classifying tests using labels #1170

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Tal-or
Copy link
Collaborator

@Tal-or Tal-or commented Jan 28, 2025

The label package contains a list of labels that can be used in
the e2e and serial tests to indicate and point certain behavior or characteristics
of the various tests.

Those can be filtered/focused by ginkgo before the test runs.

Example:
ginkgo --label-filter="!slow" means avoid any specs labelled slow

The types defined in the package are type aliases and not new defined
types. This is done in order to avoid casting every time the labels are
being used.

This package allow greater readability, prevent typos (what can easily
happen while using plain-text) and
a common place to hold and documents every label that is being
used in the tests.

Signed-off-by: Talor Itzhak [email protected]

Copy link
Contributor

openshift-ci bot commented Jan 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Tal-or

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 Jan 28, 2025
@openshift-ci openshift-ci bot requested review from mrniranjan and shajmakh January 28, 2025 08:02
The label package contains a list of labels that can be used in
the e2e and serial tests to indicate and point certain behavior or characteristics
of the various tests.

Those can be filtered/focused by ginkgo before the test runs.

Example:
`ginkgo --label-filter="!slow"` means avoid any specs labelled `slow`

The types defined in the package are type aliases and not new defined
types. This is done in order to avoid casting every time the labels are
being used.

This package allow greater readability, prevent typos (what can easily
happen while using plain-text) and
a common place to hold and documents every label that is being
used in the tests.

Signed-off-by: Talor Itzhak <[email protected]>
replace all plain-text labels with the aliases from the
label package.

There are more labels to be added, but this is a good start.

Signed-off-by: Talor Itzhak <[email protected]>
@@ -0,0 +1,72 @@
package label
Copy link
Member

Choose a reason for hiding this comment

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

missing copyright boilerplate (hack/boilerplate.go.txt)

Comment on lines +28 to +32
// Tier0 are automated unit tests
// Minimal time needed to execute (minutes to 1 hour)
// Process criteria:
// 100% automated, must-pass 100%
// Development maintains tests, and reviews result
Copy link
Member

Choose a reason for hiding this comment

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

descriptions are nice but they don't reflect what our serial tests are and wants to be

@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 31, 2025
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. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants