Tester manual

Writing suites

Author readable Tester suites with exact, reviewable steps and reusable concepts.

Keep intent visible

A suite starts with a title, optional tags and one or more test cases. Each executable line begins with an asterisk and must match a registered DSL definition.

Prefer exact UI evidence

For mobile applications, dump the UI hierarchy before asserting a label. XML page source is ground truth for accessible text; screenshots support visual assertions but should not replace structural evidence.

Use concepts for real repetition

Concepts group stable business actions. Avoid hiding a whole scenario behind one opaque phrase, and keep secrets in environment configuration rather than suite files.