How to run the tests

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36

# How to run the tests

This guide shows how to run the project's test suite before you commit. It assumes a clone of the repository and a terminal at its root.

## Run everything

```bash
make test
```

It runs the Go unit tests (`go test ./...`) and the tests of the shell tooling (`scripts/agents_test.sh`). Neither needs a real agent, a model or the network: `mm` and llmman are replaced by fakes. A green run ends with:

```text
ok      git.rickub.com/bots-garden/sidekicks/schema   …
14 passed, 0 failed
```

`make help` lists the targets.

## Run one part

| To test | Command |
| --- | --- |
| The Go packages | `make test-go`, or `go test ./schema -run Invalid -v` for one test with its output |
| `scripts/agents.sh` | `make test-scripts` |

## Variants

- **The spikes** (`spikes/acp-trace`, `spikes/wails-ui`) are separate Go modules with no unit tests; `make test` does not build them. Check them with `go vet .` inside each folder, and `npx svelte-check` in `spikes/wails-ui/frontend`.
- **Tests against real agents** do not exist yet; when they do (issue #10), they will use the `realagents` build tag and go through `scripts/agents.sh`.
- **`make: warning: Clock skew detected`** appears when the repository sits on a folder shared with another machine whose clock differs; it does not affect the result.

## See also

- What the configuration tests check → [Reference: the configuration file](../reference/configuration.md)
- The tooling under test → [Reference: scripts/agents.sh](../reference/agents-script.md)