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.

Sign up for GitHub

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

Jump to bottom

Run e2e and integration test on MacOS using github actions #5301

Closed
5 tasks
rnapoles-rh opened this issue Dec 16, 2021 · 5 comments
Closed
5 tasks

Run e2e and integration test on MacOS using github actions #5301

rnapoles-rh opened this issue Dec 16, 2021 · 5 comments
Assignees
@rnapoles-rh
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).

Comments

@rnapoles-rh
Copy link
Contributor

rnapoles-rh commented Dec 16, 2021 •
edited by dharmit
Loading

/kind feature

Which functionality do you think we should add?

Trigger tests on MacOS using github actions:

  • E2E tests
  • Integration tests

Report test results:

  • E2E tests
  • Integration tests

Why is this needed?

E2E and integration tests are required to be run on MacOS

Dependencies:

Budget approval (github actions platform costs)

  • Approved?
@openshift-ci openshift-ci bot added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label Dec 16, 2021
@rnapoles-rh rnapoles-rh mentioned this issue Dec 16, 2021
Closed
6 tasks
@rnapoles-rh rnapoles-rh added the area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering label Dec 20, 2021
@rnapoles-rh rnapoles-rh added this to For Consideration in Sprint 212 via automation Dec 20, 2021
@rnapoles-rh rnapoles-rh added the priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). label Dec 20, 2021
@dharmit dharmit removed this from For Consideration in Sprint 212 Dec 22, 2021
@dharmit dharmit added this to For Consideration in Sprint 213 via automation Dec 22, 2021
@anandrkskd
Copy link
Contributor

This PR contains the github-action workflow file and some test changes required to run test successfully.

@rnapoles-rh
Copy link
Contributor Author

rnapoles-rh commented Jan 12, 2022 •
edited
Loading

Waiting for reply from acarmona, jhorton about how billing is applied to the repo level, then pass the details to Karl for approval request.

@kadel kadel moved this from For Consideration to In Progress in Sprint 213 Jan 13, 2022
@rnapoles-rh
Copy link
Contributor Author

rnapoles-rh commented Feb 1, 2022 •
edited
Loading

GitHub actions costs can be transferred to each teams budget on a quarterly basis. QE management will discuss budget request with capex team.
If not approved we can de-risk MacOS test coverage by indirect testing during odo development once MacOS laptop refresher arrive (at least one M1 scheduled to arrive, and I have an Intel based Mac)

@joshira-rh joshira-rh removed this from In Progress in Sprint 213 Feb 2, 2022
@rnapoles-rh
Copy link
Contributor Author

For the time being we will have to do coverage through manual testing on MacOS on a periodic basis (to be defined how often)

@rnapoles-rh rnapoles-rh mentioned this issue Mar 10, 2022
Closed
9 tasks
@rnapoles-rh
Copy link
Contributor Author

We will not use github action due to high cost of Mac images

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rnapoles-rh rnapoles-rh

Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dharmit @anandrkskd @rnapoles-rh