dashboard
dashboard copied to clipboard
[Automation] - Adding data state cleanup before running cloud-credential spec
Summary
Fixes https://github.com/rancher/qa-tasks/issues/1335
Occurred changes and/or fixed issues
Adding a cleanup step to the Cloud Credential spec. This will ensure the initial state of the cloud credentials data is always empty on retries.
Areas or cases that should be tested
I've tested the remove when there are credentials linked to a cluster. I left the API check out to avoid collisions with the provisioning tests.
Areas which could experience regressions
E2E tests. Provisioning and Cloud credentials. Low risk.
Checklist
- [x] The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
- [x] The PR has a Milestone
- [x] The PR template has been filled out
- [x] The PR has been self reviewed
- [x] The PR has a reviewer assigned
- [x] The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
- [ ] The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes