Connect observed behavior to benchmark coverage
Use investigated application behavior to decide which situations need coverage or expert follow-up.
Prerequisites
An accessible Fieldloop Thread with captured sources and an identified coverage question.
Steps
- Read the report, original records, contrary examples, and relevant project objects.
- Distinguish an input-coverage discovery from a correctness claim or an unsupported report paragraph.
- Inspect supported coverage findings in Coverage Design Inbox. Review the situation and requested preparation before accepting follow-up.
- Inspect prepared Cases and adopt dataset changes through the normal review path. Request expert judgment separately when expected behavior is unresolved.
Object and state changes
Reading a Thread changes no dataset. A coverage discovery, accepted preparation, reviewed Case, and dataset adoption retain separate states.
Success criteria
The resulting benchmark change has a traceable coverage reason and an explicit adoption decision.
Common failure modes
Treating recent traffic as the full target population; treating report prose as an approved standard or automatic dataset mutation.