Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/loonghao/auroraviewWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/loonghao/auroraview/03-testing)<a href="https://agentmods.dev/rules/loonghao/auroraview/03-testing"><img src="https://agentmods.dev/badge/rules/loonghao/auroraview/03-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/loonghao/auroraview/03-testing"><img src="https://agentmods.dev/badge/rules/loonghao/auroraview/03-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00478 | $0.00478 |
| Opus 5.5 | $0.00191 | $0.00191 |
| Sonnet 5.5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
03-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
测试与 CI
测试框架与组织策略
Rust 测试框架：
-
集成测试：独立管理在
tests/目录- 测试公共 API 和完整工作流
- 使用
rstest框架提供 fixture 和参数化测试能力 - 位置：
tests/*.rs - 运行：
cargo test --test '*' --features "test-helpers"
-
测试框架依赖（dev-dependencies）：
rstest- Fixture-based 测试框架，提供类似 pytest 的 fixture 功能test-case- 表驱动测试proptest- 属性测试mockall- Mock 框架serial_test- 串行测试执行criterion- 性能基准测试
-
每个crate测试:
- 避免把单元测试内联到代码中
- 独立放到每个crate的
tests/目录中，使用rstest框架来测试
Python 测试框架：
- 使用
pytest作为主测试框架 - 位置：
tests/*.py - 运行：
pytest tests/
测试覆盖范围
- 冒烟：创建/显示/导航/resize/焦点 与 JS 消息收发
- 稳定性：睡眠/显示器切换/远程桌面 恢复；多实例并存
- 性能：首次可见 < 300ms、FPS≥60、空闲 CPU≤5%、内存增量≤200MB
CI/CD 配置
- Windows 构建矩阵（cp39–cp312 x64），签名与 WebView2 Runtime 检测提示
- Rust 集成测试在 CI 中使用
test-helpersfeature 运行 - 使用
just命令统一本地开发和 CI 环境
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 42 lines · 478 tokens per session scan A 561bcd757ab4
03-testing is a cursor rule published in the GitHub repository loonghao/auroraview (47 stars, last pushed 18d ago), licensed MIT. It adds 478 tokens to every session, about $0.0019 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
vios-testing-cicd
Testing and CI/CD conventions for VIOS.
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI, config schema and CLI packaging sync before lint, final checks, the comment on an issue a merge closes and the cleanup after the merge.
build-tags
The shipped build tag set is spelled in several places that move together.
do-no-shortcuts
Stop before every shortcut — do the proper path instead.
add-linter
Add linter configs and GitHub Actions workflows for languages detected in the current repo. Use when the user wants to add linters, set up code quality checks, or after sync-scaffold suggests running /add-linter.
testing-ci-rule
testing-ci-rule from DaunteEth/woofi-pro-mcp.