Scenarios and personas
Prepare executable checks and reproducible user conditions
A scenario defines what to verify. A persona defines the user conditions for the check. The environment and browser also need to match when comparing results.
Executable scenarios
A scenario needs metadata such as its name, description, tags, steps, and expected results, plus code that performs the checks. Saving a list of steps alone does not make a browser perform every action or assert every outcome.
- Open Verification → Test list and choose New test.
- Define actions and expected outcomes, then check required environment variables.
- Verify that the code performs the actions and asserts the expected results.
- Save the test, select it in the run dialog, and review execution conditions before running.
To use AI, start from Verification → Test list → Generate with AI. Review generated selectors, authentication, assertions, and changed files before applying the draft. Existing tests can be edited through their code and metadata editor.
Repository-based Playwright scenarios use test-case.json for metadata and index.spec.ts for executable code. Scenario drafts from the service map also need executable checks.
Configure a persona
Create a persona in Settings → Personas, or duplicate a template.
| Category | Configuration |
|---|---|
| User context | Name, description, role, plan, experience level, and goals |
| Screen and language | Desktop, tablet, mobile, or custom viewport; locale |
| Authentication | Whether login is required; credentials or stored-session strategy |
| Environment | Target environment and environment-specific bindings |
| Feature conditions | Feature overrides passed to tests |
Templates are starting points. Fill in required environments and credentials, then check readiness indicators. Naming a persona “Pro user” or “Administrator” does not grant that account permissions in the actual service. Feature overrides do not grant server permissions either.
Run the same flow under different conditions
For example, run a booking-history scenario for a Korean-speaking member on a mobile viewport and an English-speaking member on a desktop viewport. Prepare each account's test data and assert the expected behavior for its conditions.
Viewport settings change the browser's screen dimensions. They do not verify every hardware or operating-system behavior of a real mobile device.
Before rerunning
- Check whether the code changed and whether assertions still match product requirements.
- Confirm the URL, account, session, and test data are ready.
- Match browser, language, and screen conditions when comparing runs.
A rerun uses current test definitions and settings. Selecting a historical report does not restore its original code or account state. See Reports and analytics for interpreting results.