Test real object
| Who will use it for what purpose? | paperclip for teachers to fasten paper |
|---|---|
| Example use cases | send/receive/read/write/erase |
| Bounds of use (env factor temp, bounds) | max 30 paper |
| Stress/fail conditions (what's acceptable) | |
| How to perform testing (reasonable number assumptins) |
Camera: Take photo, photo management, settings
Test software
| 1. Blackbox testing, whitebox testing, or both |
|---|
| 2. Who use for what (parent implement blocking, children receipt block, guests?) |
| 3. Use case examples? (parents-install/update/remove control, personal usage; 子(il)legal content |
| 4. Bounds of use. (action against illegal content. block image? block entire site? |
| 5. Stress/failure conditions (expected failure behavior, design pwd override for parents? |
| 6. Test cases and how? Manual vs automated? Be organized with categories. |
Test function
| 1. Define test cases: Normal (代表性的odd/even); Extreme(empty,1,huge); Nulls/Illegals; Strange input(reverse sorted) |
|---|
| 2. Define Expected results (output; original input intact; in-place no extra memory; stable-strict order |
| 3. Write test code (AssertEquals...) |
Debug issue
| 1. Understanding scenario: (problem for how long? OS version? consistent? how often? error report? logs? reproducable? |
|---|
| 2. Break down the problem. (steps. Start, launch, open, load setting, HTTPs, parse, render) |
| 3. Create specific, manageable tests |
What interviewers looking for
- Big picture understanding: Priotize (reliable payments more important than product images)
- Knowing pieces fit together: Test integration with Gmail, plugins, components etc
- Organization: Structured manner! Break down parts into categories
- Practicality: feasible and realistic tests