基于属性的测试
- 作者仓库星标 0
- 作者更新于 2026年8月24日 23:09
- 作者仓库 skills
- 领域
- 文档
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @trailofbits · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
# Property-Based Testing
An example test asserts one point. A property asserts a rule over the whole input
domain and lets the generator hunt for the counterexample. That trade is worth making
when the code has an algebraic shape — an inverse, an invariant, an oracle — and not
otherwise. Code with no such shape gets example tests; saying so is a valid outcome.
Check first whether the shape is missing or merely buried. A calculation wrapped in I/O,
a string built by concatenation, an in-place mutation — each has a property and no seam
to assert it through. See [references/refactoring.md](references/refactoring.md) before
concluding there is nothing to assert.
## Property catalog
| Property | Formula | Where it applies |
|---|---|---|
| Roundtrip | `decode(encode(x)) == x` | Serialization, conversion pairs |
| Inverse | `f(g(x)) == x` | encrypt/decrypt, compress/decompress |
| Oracle | `new(x) == reference(x)` | Optimization, refactoring, reimplementation |
| Idempotence | `f(f(x)) == f(x)` | Normalization, formatting, sorting |
| Invariant | Holds before and after | Any transformation, contract state |
| Easy to verify | `is_sorted(sort(x))` | Complex algorithms with cheap checkers |
| Commutativity | `f(a, b) == f(b, a)` | Binary and set operations |
| Associativity | `f(f(a,b), c) == f(a, f(b,c))` | Combining operations |
| Identity | `f(x, e) == x` | Operations with a neutral element |
Strength ordering, weakest to strongest:
`no crash → type preservation → invariant → idempotence → roundtrip / oracle`.
Assert the strongest property the code supports. "No crash" alone rarely justifies the
dependency — if that is all you can find, either a small rearrangement exposes something
stronger, or the honest report is that this code is a poor PBT candidate. Rule out the
first before settling for the second.
## The two ways a property test asserts nothing
- **Tautology.** `assert add(a, b) == a + b` restates the implementation; no bug they
share can fail it. Pick a property that constrains the function without recomputing
it. Note the exception: `f(x) == f(x)` is a genuine determinism property when `f`
is not obviously pure — serializers over dicts or sets, hashing, anything reading
the clock.
- **Vacuity.** `assume()` that filters out nearly every input passes without
exercising anything, and self-contradictory `assume()` passes having run zero cases.
Push constraints into the strategy so the generator produces valid inputs directly.
## Where to look next
Load the one that matches the task in front of you:
| Task | File |
|---|---|
| Writing new tests, designing strategies | [references/generating.md](references/generating.md) |
| The code has no property to assert yet | [references/refactoring.md](references/refactoring.md) |
| Reviewing existing property tests | [references/reviewing.md](references/reviewing.md) |
| A property test just failed | [references/interpreting-failures.md](references/interpreting-failures.md) |
| Library choice, Echidna and Medusa | [references/libraries.md](references/libraries.md) |
## Introducing PBT to a project that lacks it
If the project already uses a PBT library, just write the tests in it. If it does not,
adding one is a dependency decision that belongs to the user — offer it once with the
specific property you would write, and take the answer either way.
章节与文件索引
按说明文件中的顺序排列。
房产目录
属性测试不断言的两种方式
下一步该看哪里
将 PBT 引入缺乏 PBT 的项目
文件/命令 -> decode(encode(x)) == x · f(g(x)) == x · new(x) == reference(x) · f(f(x)) == f(x) · is_sorted(sort(x)) · f(a, b) == f(b, a) · f(f(a,b), c) == f(a, f(b,c)) · f(x, e) == x
内容校验值 -> d99233df49df
当前原文的自动摘译,尚未人工审校。
房产目录
属性 · 公式 · 适用范围 往返 ·
decode(encode(x)) == x· 序列化、转换对 逆向 ·f(g(x)) == x· 加密/解密、压缩/解压 Oracle ·new(x) == reference(x)· 优化、重构、重新实现 幂等性 ·f(f(x)) == f(x)· 规范化、格式化、排序属性测试不断言的两种方式
同义反复。
assert add(a, b) == a + b重申实施;他们分享的任何错误都不会失败。选择一个属性来约束函数而不重新计算它。请注意例外:当f显然不是纯的时,f(x) == f(x)是一个真正的确定性属性——字典或集合上的序列化器、散列、任何读取时钟的东西。下一步该看哪里
加载与您面前的任务相匹配的任务: 任务·文件 编写新测试,设计策略·references/generate.md 代码还没有要断言的属性·references/refactoring.md 审查现有属性测试·references/reviewing.md
将 PBT 引入缺乏 PBT 的项目
如果项目已经使用PBT库,只需在其中编写测试即可。如果没有,添加一个是属于用户的依赖决策 - 使用您要编写的特定属性提供一次,然后以任一方式获取答案。