You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,7 @@ This file is the canonical repository guidance for coding agents working in `okd
5
5
## Workflow
6
6
7
7
- Prefer targeted, repo-relevant tests before committing.
8
+
- Clean up resources created by ad-hoc e2e tests before finishing the task.
8
9
- Prefer `rg` and `rg --files` for search.
9
10
- Keep changes narrow and preserve existing patterns unless the task requires a broader refactor.
10
11
- Update user-facing docs when behavior changes.
@@ -31,9 +32,16 @@ This file is the canonical repository guidance for coding agents working in `okd
31
32
- When asked to update a local install to a release, prefer the published release asset over a workspace build.
32
33
- For release follow-ups, verify the actual published artifact or image rather than assuming the workflow succeeded.
33
34
35
+
## E2E Testing Rules
36
+
37
+
- Prefer the smallest realistic end-to-end check that validates the changed behavior.
38
+
- Reuse existing local installs, release binaries, and published sidecar images when they are sufficient for the test.
39
+
- If an e2e test creates cluster resources, local background processes, SSH config entries, port-forwards, or temporary files, clean them up before finishing unless the user explicitly asks to keep them.
40
+
- For `okdev` session tests, prefer tearing down with `okdev down` after verification when the session was created only for the test.
41
+
- If cleanup cannot be completed, say exactly what was left behind and where.
42
+
34
43
## Repo-Specific Expectations
35
44
36
45
- Keep sidecar, SSH, tmux, and Syncthing behavior aligned; changes in one often require checking the others.
37
46
- Be careful with config-loading output paths because many commands share the same helper logic.
38
47
- When changing pod or sidecar behavior, consider both local installs and sidecar image rebuild/publish steps.
0 commit comments