Friend list

[zelytra]

Description of needs

Drafts or UI templates

Acceptance criteria (done when...)

Tip: Write a checkboxed list of sentences in the present tense describing the desired state of the system.

GOOD (clear how to verify, it reports design and interaction decisions
agreed):

• The page shows a button only to logged in users
• The button has the style XXX and label "Logout"
• When pressed, opens a confirmation modal with "OK" and "Cancel" buttons
• ...

BAD (cannot be activated during verification, too arbitrary):

• Logout button
• Modal for confirmation

Validation scenarios

Hint: Use Gherkin syntax to lay them out. It is complete and explicit, human-readable but easy to convert into self-executable tests.

Tip: A scenario title should describe in a complete sentence what happens in that scenario, to improve readability and indability.

OK: Administrator logs into back-office
BAD: Backoffice login

Tasks

This section is populated by the developer and reports the expected practical activities to meet the requirements. Useful for estimating and for day-by-day monitoring. Better if it reports checkboxes to track completion.

• Task 1
• Task 2
• ...

Notes