Skip to content

Identify tests that can be automated for Openshift Local Extension #533

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

Closed
rujutashinde opened this issue Feb 10, 2025 · 1 comment
Closed

Comments

@rujutashinde
Copy link

This issue is to track the work to identify tests to be automated, in the Openshift Local Extension Testing Tracker google sheet .

  • Go through each row in the tracker sheet and verify if the test mentioned can be automated.
  • If so, create a sub-task under this epic or a sub-task under a separate epic on github to track the work that would go into automating this test and add label qe/test-case
  • If the issue has to be in the extension repo, add it there instead with the label qe/test-case. Create the label if not present
  • Add that github issue link in the Automation column in the sheet.
  • If there is an existing ticket for the identified test, use that issue link instead
  • Document/Communicate as required
  • This will build the automation backlog which we can track and work through.
@danivilla9
Copy link
Collaborator

I used the previously existing epic to list the newly created issues: #502, the testing tracker has been updated too. I think I'm not missing anything!

@danivilla9 danivilla9 moved this from 📅 Planned to 🚥 In Review in Podman Desktop Planning Mar 6, 2025
@danivilla9 danivilla9 moved this from 🚥 In Review to ✔️ Done in Podman Desktop Planning Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants