Validation
Validation scenarios.Observed, pending, or blocked.
Every validated entry was actually run and observed. Pending work is listed with where it still needs to run. Blocked scenarios stay visible with the reason — no invented coverage. Scenarios record where detection was tested; the checks reference explains how each signal works.
- Validated
- 23
- Pending
- 5
- Blocked
- 3
- Showing
- 17
How to read this list
Each scenario is one test case. Its code says where it runs; its status says whether it has been run.
- U · Automated
- Automated test that runs on every code change — no device.
- B · Build & packaging
- Build or packaging check — does the package install and compile.
- S · Simulator / emulator
- Run on a simulator or emulator — a virtual device on a computer.
- D · Real device
- Run on a real phone, used normally.
- A · Adversarial
- Run on a real phone that's been attacked or modified — rooted, jailbroken, hooked or hidden.
- Validated
- Run, and the result matched what was expected.
- Pending
- Not run yet. The expected result is written down; there is no observed result.
- Blocked
- Can't be run right now — the reason is on the page.
Automated
Automated2 scenarios
Build & packaging
Build & packaging1 scenario
Emulator
Emulator10 scenarios
Adversarial