Test Authoring Workflow

Test authoring in Drizz refers to the process of writing automation steps as clear, intent-driven commands that mirror real user actions on the application. Unlike record-and-playback tools, Drizz enables scriptless yet precise authoring, where each line is crafted based on what is visible on the device screen. This section outlines the complete authoring workflow including writing, editing, structuring, and modularizing tests to ensure clarity, maintainability, and deterministic execution across environments.

Writing a Test:

1. Launch the application under test.

2. Begin writing commands based on the visible screen.

3. Each command represents a single user intent or interaction.

4. Commands are added sequentially as the flow progresses.

5. Continue authoring commands until the desired end state is reached.

6. Save the test once the full flow is defined.

Editing a Test:

1. Open the test to review the written commands.

2. Modify commands to refine intent or behavior.

3. Reorder, insert, or remove commands as needed.

4. Update inputs, conditions, or expected outcomes.

5. Save changes to apply them across executions.

Key Characteristics:

1. Tests follow a linear, screen-by-screen flow

2. Commands remain human-readable and editable

3. No dependency on recordings or replays

4. Designed for long-term maintainability and clarity

Module Usage

Commands or sequences may be moved into reusable modules.

Eg. Login module