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: .cursor/skills/console-tests/SKILL.md
+32-1Lines changed: 32 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
name: console-tests
3
-
description: Run and interpret tests in the Console Elixir repo. Use when validating changes with `mix test`, running Docker integration tests, diagnosing sandboxnetwork failures, or explaining Console test setup in Cursor.
3
+
description: Run and interpret tests in the Console repo. Use when validating changes with `mix test`, running deployment-operator Go tests, diagnosing sandbox/toolchain/network failures, or explaining Console test setup in Cursor.
4
4
---
5
5
6
6
# Console Tests
@@ -10,8 +10,19 @@ Use this skill when validating changes in the Console repo.
10
10
## Sandbox Requirements
11
11
12
12
- Run `mix test` commands from the repo root: `/Users/michaelguarino/code/console`.
13
+
- Run deployment-operator Go commands from `/Users/michaelguarino/code/console/go/deployment-operator`.
13
14
- The default Cursor sandbox blocks some domains the Console app touches during startup and test aliases.
14
15
- Use `required_permissions: ["full_network"]` for `mix test` runs that need the normal project setup.
16
+
- For Go tests, explicitly set Go caches inside the workspace when running in the sandbox:
17
+
18
+
```bash
19
+
cd /Users/michaelguarino/code/console/go/deployment-operator && \
- Use `required_permissions: ["full_network"]` for Go tests when dependencies or the configured Go toolchain need to download. If Go still fails writing to `/Users/michaelguarino/go/pkg/...`, rerun with the in-workspace `GOPATH`/`GOCACHE` above before requesting `all`.
15
26
- Do not run `mix format` in this repository.
16
27
17
28
## Why Full Network Is Needed
@@ -38,16 +49,36 @@ Full suite:
38
49
mix test
39
50
```
40
51
52
+
Focused deployment-operator service package:
53
+
54
+
```bash
55
+
cd /Users/michaelguarino/code/console/go/deployment-operator && \
- A focused test passing is good validation for narrow changes, especially when the full suite is known to depend on external/local fixtures.
45
72
- Full-suite failures like `could not resolve ref main` or `could not resolve ref master` usually indicate git fixture/ref setup problems unless the touched code is in that path.
73
+
- Go failures like `go.work requires go >= 1.26.5` can mean the IDE/linter is using an older local Go. A shell `go test` may still work through Go's auto toolchain download when network and cache permissions are set correctly.
74
+
- Sandbox errors writing under `/Users/michaelguarino/go/pkg/sumdb` indicate the Go module/toolchain cache is outside the writable workspace. Prefer setting `GOPATH` and `GOCACHE` inside `/Users/michaelguarino/code/console`.
46
75
- Report full-suite failures honestly, but separate environment/fixture failures from failures in the files being changed.
47
76
48
77
## Validation Checklist
49
78
50
79
-[ ] Run the most relevant focused test file with `full_network` if it uses project startup or external services.
80
+
-[ ] For deployment-operator Go changes, run `gofmt -w` on touched files from the module directory.
81
+
-[ ] For deployment-operator Go tests, `cd` into `go/deployment-operator` and use in-workspace `GOPATH`/`GOCACHE` when sandboxed.
51
82
-[ ] Run the full suite with `full_network` when requested or when the change has broad impact.
52
83
-[ ] Read the final ExUnit summary and any failure blocks for touched modules.
53
84
-[ ] Run `ReadLints` on changed files after edits.
0 commit comments