Skip to content

Conversation

DavidRajnoha
Copy link
Contributor

Add @cypress/grep plugin integration with tag-based test filtering:

  • Register grep plugin in cypress.config.ts and support/index.ts
  • Tag test files: @smoke (5), @regression (3), @slow (1), @demo (1)
  • Update README with tag usage documentation

Tags enable flexible test execution:
npx cypress run --env grepTags=@smoke # BVT tests only
npx cypress run --env grepTags=@regression # Regression tests
npx cypress run --env grepTags="-@slow -@demo" # Exclude long/demo tests
npx cypress run --env grepTags="@smoke @regression" # Combined (OR)

Add @cypress/grep plugin integration with tag-based test filtering:

- Register grep plugin in cypress.config.ts and support/index.ts
- Tag test files: @smoke (5), @regression (3), @slow (1), @demo (1)
- Update README with tag usage documentation

Tags enable flexible test execution:
  npx cypress run --env grepTags=@smoke              # BVT tests only
  npx cypress run --env grepTags=@regression         # Regression tests
  npx cypress run --env grepTags="-@slow -@demo"     # Exclude long/demo tests
  npx cypress run --env grepTags="@smoke @regression" # Combined (OR)
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 15, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 15, 2025

@DavidRajnoha: This pull request references OBSINTA-857 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

In response to this:

Add @cypress/grep plugin integration with tag-based test filtering:

  • Register grep plugin in cypress.config.ts and support/index.ts
  • Tag test files: @smoke (5), @regression (3), @slow (1), @demo (1)
  • Update README with tag usage documentation

Tags enable flexible test execution:
npx cypress run --env grepTags=@smoke # BVT tests only
npx cypress run --env grepTags=@regression # Regression tests
npx cypress run --env grepTags="-@slow -@demo" # Exclude long/demo tests
npx cypress run --env grepTags="@smoke @regression" # Combined (OR)

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from kyoto and zhuje October 15, 2025 14:03
@zhuje
Copy link
Contributor

zhuje commented Oct 16, 2025

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 16, 2025

@DavidRajnoha: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@zhuje
Copy link
Contributor

zhuje commented Oct 17, 2025

/lgtm

/ux-approved

No UX changes

@zhuje
Copy link
Contributor

zhuje commented Oct 17, 2025

@etmurasaki Can you take a look too? I left the 'qe-approved' label for you to apply.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 17, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: DavidRajnoha, zhuje

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 Oct 17, 2025
@DavidRajnoha
Copy link
Contributor Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 20, 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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants