Skip to content

Document how to re-run pytest from scratch. #585

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

Merged
gaelgatelement merged 1 commit into from
Jun 30, 2025
+5 −1
Merged

Document how to re-run pytest from scratch. #585

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion DEVELOPERS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
<!--
Copyright 2024 New Vector Ltd
Copyright 2024-2025 New Vector Ltd
SPDX-License-Identifier: AGPL-3.0-only
-->
Expand Down Expand Up @@ -153,6 +153,9 @@ Verifies that the deployed workloads behave as expected and integrates well toge

From the project root : `pytest test`

Pytest caches the namespace name and created user tokens between run. To start a run from scratch,
run `pytest test --cache-clear`.

#### Special env variables
- `PYTEST_KEEP_CLUSTER=1` : Do not destroy the cluster at the end of the test run.
You must delete it using `kind delete cluster --name ess-helm` manually before running any other test run.
Expand Down
1 change: 1 addition & 0 deletions newsfragments/579.changed.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
Document how to re-run integration tests from scratch.
0 newsfragments/584.changed.md → newsfragments/585.changed.md
View file
Open in desktop
File renamed without changes.
Loading
⚡