Testing guidelines

[Utzel-Butzel]

Golden rules

• One problem per ticket
• Use the right repo for the ticket (paperlesspaper-web if not sure)
• Write for someone who didn’t see it: include context, expected vs actual, and evidence.
• State impact in user terms (“blocks sending images”, “wrong VAT total”, “setup instructions incorrect”).
• Meaningful title
• Do not share any user data.
• If it is a more general idea or feedback use Discussions
• Please be nice :)

Examples of well-written tickets

Example 1 — Checkout bug (high impact)

Title: Black screen during OTA update when cold

Steps

Outside temperature is cold
→ Reset device
→ sleep screen shows up
→ Press button

Expected

See the OTA screen or the device onboarding screen

Actual

black screen

Acceptance Criteria

Content should be always visible

Use different update handler during cold temperatures (slow update), that is not effected by cold temperatures

For copy & paste

### Steps
–
→ –
→ –
→ –

### Expected
–

### Actual
–