基础设施与运维
cost-control-testing
更新于 2026-08-19
Cloud Cost Control · 测试规则
Testing rules for Cloud Cost Control: behaviour-named cases, explicit fixtures and order-independent suites.
- 技术栈
- Cloud Cost Control
- 主题
- 测试
- 条目
- 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
◎ 交付前验证
- ◎ Rebuild the host from the bootstrap path at least once
- ◎ Port scan matches the intended surface
- ◎ Backups restored successfully into a scratch environment
同分类条目
38 篇基础设施与运维
Docker 工程规则
Production Dockerfile rules: minimal multi-stage images and non-root runtime
基础设施与运维
Docker Compose 工程规则
Compose rules: explicit healthchecks, pinned images and network segmentation
基础设施与运维
Kubernetes 工程规则
Kubernetes rules: resource limits, readiness probes and rolling-update safety
基础设施与运维
Helm 工程规则
Helm rules: values schema validation and template-time guard rails
基础设施与运维
Terraform 工程规则
Terraform rules: locked remote state, reviewed plans and no console drift
基础设施与运维
Ansible 工程规则
Ansible rules: idempotent tasks, changed_when discipline and vaulted secrets