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

[UI] - Adding CIS chart UI tests #13194

Merged
merged 1 commit into from
Jan 30, 2025
Merged

Conversation

izaac
Copy link
Contributor

@izaac izaac commented Jan 23, 2025

Summary

Fixes #
rancher/qa-tasks#1547

Occurred changes and/or fixed issues

Adding p0 tests for the UI chart. Includes install and a Scan. Basic functionality.
As well as a YAML view check.

Areas or cases that should be tested

E2E tests. CI

Areas which could experience regressions

CI

Checklist

  • The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
  • The PR has a Milestone
  • The PR template has been filled out
  • The PR has been self reviewed
  • The PR has a reviewer assigned
  • The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed

@izaac izaac added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jan 23, 2025
@izaac izaac added this to the v2.12.0 milestone Jan 23, 2025
@izaac izaac requested review from a-arias and yonasberhe23 January 23, 2025 20:53
@izaac izaac self-assigned this Jan 23, 2025
@izaac izaac marked this pull request as ready for review January 27, 2025 15:41
@izaac
Copy link
Contributor Author

izaac commented Jan 27, 2025

I am moving this to ready as I did a few rounds of testing to see if the Scan Active check was appropriate in this case.

I originally thought on only checking creation as that'd be sufficient for the test but checking for Active could be more useful as the Permissive CIS profile has to pass on each release. Otherwise it's a backend bug.

@izaac izaac force-pushed the cis-benchmark-tests branch 2 times, most recently from a76221d to 8da5cea Compare January 29, 2025 16:46
Copy link

@a-arias a-arias left a comment

Choose a reason for hiding this comment

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

looks good 👍

@izaac izaac requested a review from yonasberhe23 January 29, 2025 20:27
@izaac izaac force-pushed the cis-benchmark-tests branch 2 times, most recently from 1f02374 to 784237f Compare January 29, 2025 23:09
@izaac izaac requested a review from yonasberhe23 January 29, 2025 23:23
@izaac izaac force-pushed the cis-benchmark-tests branch from 784237f to 3d9633e Compare January 30, 2025 21:15
@izaac izaac requested a review from a-arias January 30, 2025 21:16
Copy link
Contributor

@yonasberhe23 yonasberhe23 left a comment

Choose a reason for hiding this comment

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

2 improvements. otherwise looks good!

return new NameNsDescription(this.self());
}

saveCreateForm(): AsyncButtonPo {
Copy link
Contributor

Choose a reason for hiding this comment

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

this can be removed since you already have cruResource()

return new ResourceListMastheadPo(this.self());
}

createLoggingFlow() {
Copy link
Contributor

Choose a reason for hiding this comment

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

update name and utilize in test on line 66

@izaac izaac force-pushed the cis-benchmark-tests branch from 3d9633e to c0dfe0e Compare January 30, 2025 22:40
@izaac izaac merged commit 763840d into rancher:master Jan 30, 2025
32 checks passed
@izaac izaac deleted the cis-benchmark-tests branch January 30, 2025 23:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants