Skip to content

Fix existing E2E test failures and Improve resource cleanup #37

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

Merged
merged 11 commits into from
Apr 9, 2025
Merged
4 changes: 2 additions & 2 deletions e2e/Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ e2e tests for the Civo Cloud Controller Manager.
These tests can be run:

```bash
CIVO_API_KEY=.... go test --timeout 30 -v ./e2e/...
CIVO_API_KEY=.... go test -timeout 20m -v ./...
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note

The command was incorrect, so I have fixed it. Additionally, since it didn't finish within 30 seconds, I have changed the timeout to 20 minutes.

```

or the CIVO_API_KEY can be set in the `.env` file in the root of the project
Expand All @@ -21,7 +21,7 @@ The general flow for each test is as follows:
1. Provision a new cluster
2. Wait for the cluster to be provisioned
2. Scale down pre-deployed CCM in the cluster
4. Run the local copy of CCM
4. Run the local copy of CCM
5. Run e2e Tests
6. Delete the cluster

Expand Down
Loading