How should you define a mobile problem?
State what happened and what should have happened, using specific, observable details.
Study Mobile Issue Reporting and Reproduction with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.
How should you define a mobile problem?
State what happened and what should have happened, using specific, observable details.
What makes a problem description observable?
Replace vague labels with observable behavior, such as the exact screen message and what did not appear.
Observed result versus expected result?
The observed result is what actually happened; the expected result is what should have happened.
What context should accompany a mobile issue report?
Record when it began, how often it occurs, whether it affects one or all items, and whether it followed a change.
How should an error message be documented?
Copy the exact error text rather than paraphrasing it.
What makes reproduction steps repeatable?
Use a short, numbered sequence that another person can follow from a known starting state.
How should a reproduction test be conducted?
Begin with a known starting state, perform the same actions, and record the outcome.
What should be recorded while reproducing an issue?
Record whether it happens every time or intermittently, and note relevant timing, such as whether the app was foregrounded or idle.
How should you investigate an intermittent failure?
Repeat the same test and compare conditions; change only one factor at a time.
Why change only one factor at a time?
Changing one condition at a time helps reveal which conditions affect the result.
How can connection type be tested as a condition?
Compare the same test using Wi-Fi versus cellular data, changing only the connection type.
How can account choice be tested as a condition?
Compare one account with another while keeping the rest of the test consistent.
Focused study of installation failures, crashes and application compatibility.
Focused study of recognition, isolation and remediation workflow concepts.
Focused study of symptoms, diagnostic steps and common operating-system failures.