leviso-cheat-test 0.1.3

Proc-macro for cheat-aware test documentation
Documentation 
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
37
38

# CLAUDE.md - cheat-test

## What is cheat-test?

Proc-macro crate for cheat-aware test attributes. Forces documentation of how tests could be cheated.

## What Belongs Here

- Proc-macro definitions only
- `#[cheat_aware]`, `#[cheat_reviewed]`, `#[cheat_canary]`

## What Does NOT Belong Here

| Don't put here | Put it in |
|----------------|-----------|
| Runtime macros | `testing/cheat-guard/` |
| Actual tests | `testing/install-tests/` or `testing/rootfs-tests/` |

## Commands

```bash
cargo build
cargo test    # Note: proc-macro tests are tricky
```

## Macros

| Macro | Purpose |
|-------|---------|
| `#[cheat_aware]` | Full cheat documentation for user-facing tests |
| `#[cheat_reviewed]` | Acknowledgment test was reviewed |
| `#[cheat_canary]` | Honeypot that alerts if modified |

## Key Rules

1. Don't remove cheat metadata fields
2. Don't simplify output - verbose failures are intentional
3. Don't weaken severity levels