PlayStore12TesterSee how a finding can be communicated to a developer. This page illustrates the report format; it is not a customer result, a real device test or a success statistic.
SAMPLE REPORT · NOT A REAL TEST RUN
Finding summary
- Document type
- Illustrative example; not an actual testing campaign.
- Example ID
- SAMPLE-UI-001
- Area
- Primary action on a small screen
- Severity
- Example assessment: medium
- Environment
- Scenario assumption: 320 CSS px viewport, large text
- Build
- Illustrative app; no actual build or device measurement.
- Retest
- Pending; no fix or successful retest is claimed.
Steps to reproduce
- Open the illustrative app’s starting screen.
- Set the viewport width to 320 CSS px.
- Increase text size and inspect the screen with a long button label.
- Record whether the full action remains visible and usable.
Expected behavior
The label remains readable, the primary action stays accessible and the screen works without horizontal scrolling.
Illustrative finding
Long text extends beyond a fixed-height button. This describes a report example, not a measured result.
Fix and retest record
The developer records the change and new build. The same scenario is run again and marked passed, failed or not verified. An actual report records only outcomes that were observed.
Your actual report depends on the agreed scope and observed findings, and is delivered by email.