Writing Clear Instructions

To get the most out of tapioka.ai, instructions should be written in a simple, precise, and unambiguous way. Think of it as writing for someone who has never seen your application before.

Core Rules

1. Start from the Beginning

Every instruction is assumed to start from the app's initial state (e.g., the Home Screen after a fresh launch).

2. Ensure Repeatability

Instructions should not change the application state stored in the backend in a way that breaks future runs.

• Allowed: Login/Logout (transient session state).
• Avoid: Adding/Deleting unique items (if it makes the test non-repeatable).

3. Functional over Technical

Describe what to do, not how to do it technically. Avoid describing UI elements like "checkboxes" or "divs" unless the AI fails to understand a simpler command.

• Good: "...then accept the terms and conditions."
• Avoid: "...then click the 'accept' checkbox next to the terms and conditions."

4. No Logic Branches

Instructions should be a straight path. Do not use "if/else" or branches (e.g., "Go to X and if the user is logged in, do Y"). Note: This rule does not apply to Preconditions.

Examples

• Standard Flow:
  • "Go to Your Account, then Settings, and finally show the list of devices."
• Search Flow:
  • "Go to the search bar, search for 'Game of Thrones', and open the series page."
• TV/Media Flow:
  • "Go to TV, then view the TV Program."