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

[Refactor] Move CAPI related E2E tests to one place. #1476

Closed
geetikabatra opened this issue Mar 14, 2022 · 4 comments
Closed

[Refactor] Move CAPI related E2E tests to one place. #1476

geetikabatra opened this issue Mar 14, 2022 · 4 comments
Assignees
Labels
area/testing kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@geetikabatra
Copy link
Contributor

/kind bug

What steps did you take and what happened:

Currently, all CAPI related E2E tests are written in different files. The idea is to consolidate all the CAPI related E2E tests in one place. This will bring more structure to the code base.

What did you expect to happen:
N/A

Anything else you would like to add:
N/A

Environment:

  • Cluster-api-provider-vsphere version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Mar 14, 2022
@srm09
Copy link
Contributor

srm09 commented Mar 17, 2022

Like we talked about, let us keep the refactoring for a later point in time until we have stable E2E tests running for a period of time.
/lifecycle frozen
/remove-kind bug
/kind cleanup
/area testing

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. area/testing and removed kind/bug Categorizes issue or PR as related to a bug. labels Mar 17, 2022
@chrischdi
Copy link
Member

chrischdi commented Aug 17, 2023

/assign @killianmuldoon

For updating here and linking what work we already want to do

@killianmuldoon
Copy link
Contributor

/close

I'm taking a look at restructuring some of the test directory - starting with #2251. Will take this into account when thinking about consolidating existing tests.

@k8s-ci-robot
Copy link
Contributor

@killianmuldoon: Closing this issue.

In response to this:

/close

I'm taking a look at restructuring some of the test directory - starting with #2251. Will take this into account when thinking about consolidating existing tests.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

5 participants