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

New odo testing system #5162

Closed
7 of 9 tasks
kadel opened this issue Oct 21, 2021 · 2 comments
Closed
7 of 9 tasks

New odo testing system #5162

kadel opened this issue Oct 21, 2021 · 2 comments
Labels
area/infra Issues or PRs related to setting up or fixing things in infrastructure. Mostly CI infrastructure. area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks

Comments

@kadel
Copy link
Member

kadel commented Oct 21, 2021

We need to get into the point where we have tests running for each PR and also periodic/nightly jobs.

Jobs executed for each PR

The PR tests should verify that the code that is about to get merge works.
All PR tests are executed on IBM Cloud, and OCP cluster can be of any stable version.

The periodic/nightly jobs

Jobs should verify that what is in odo main branch works with all supported OCP versions.
All nightly jobs are executed using OpenShift CI (Prow)

  • integrations tests executed from linux against all supported OCP versions (usually the latest one and 2 previous versions)
  • integrations tests executed from linux against future OCP version (passing is optional)

/kind test
/area infra

@openshift-ci openshift-ci bot added the area/infra Issues or PRs related to setting up or fixing things in infrastructure. Mostly CI infrastructure. label Oct 21, 2021
@openshift-ci
Copy link

openshift-ci bot commented Oct 21, 2021

@kadel: The label(s) kind/test cannot be applied, because the repository doesn't have them.

In response to this:

We need to get into the point where we have tests running for each PR and also periodic/nightly jobs.

The PR tests should verify that the code that is about to get merge works.
Jobs that should be executed for each PR:

  • unit tests started on linux
  • unit tests started on windows
  • unit tests started on mac
  • integrations test executed from mac against OCP cluster
  • integrations tests executed from linux against the latest stable kubernetes cluster (can be minikube)

The periodic/nightly jobs should verify that what is in odo main branch works with all supported OCP versions.

  • integrations test executed from linux against OCP cluster (ideally the latest stable one, but it can be any supported version)
  • integrations test executed from windows against OCP cluster (ideally the latest stable one, but it can be any supported version)
  • integrations tests executed form linux against all supported OCP versions (usually the latest one and 2 previous versions)
  • integrations tests executed from linux against future OCP version

/kind test
/area infra

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/test-infra repository.

@kadel kadel added kind/tests kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks labels Oct 21, 2021
@rnapoles-rh rnapoles-rh self-assigned this Oct 21, 2021
@kadel kadel added area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering and removed kind/tests labels Feb 16, 2022
@rnapoles-rh rnapoles-rh removed their assignment Feb 24, 2022
@rnapoles-rh
Copy link
Contributor

Tracking the MacOS portion with #5301

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra Issues or PRs related to setting up or fixing things in infrastructure. Mostly CI infrastructure. area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks
Projects
None yet
Development

No branches or pull requests

2 participants