测试与质量
go-testing-testing
更新于 2026-09-26
Go Testing · 测试规则
Testing rules for Go Testing: behaviour-named cases, explicit fixtures and order-independent suites.
- 技术栈
- Go Testing
- 主题
- 测试
- 条目
- 9 条
- 版本
- v0.2.0
✓ 应当这么做
- ✓ Test the smallest unit that carries the behaviour, then one end-to-end happy path
- ✓ Name tests after the behaviour, not after the function under test
- ✓ Keep fixtures explicit and local to the test that needs them
✕ 常见反模式
- ✕ Asserting on private internals that will change with any refactor
- ✕ Fixed sleeps instead of condition waits
- ✕ Tests that depend on execution order or a shared mutable world
◎ 交付前验证
- ◎ Suite passes in random order and with concurrency enabled
- ◎ Coverage on the changed module did not drop
- ◎ Flaky tests reported rather than retried silently
同分类条目
27 篇测试与质量
Vitest 工程规则
Vitest rules: behaviour-first assertions and deterministic concurrency
测试与质量
Jest 工程规则
Jest rules: boundary mocks, isolated modules and no shared global state
测试与质量
Playwright 工程规则
Playwright rules: role-based selectors and network idempotency
测试与质量
Cypress 工程规则
Cypress rules: spec independence and explicit API seeding
测试与质量
Go Testing 工程规则
Go testing rules: table-driven cases and race-detector runs
测试与质量
pytest 工程规则
pytest rules: fixture scoping and no inter-test ordering assumptions