Order of actions when writing new tests

1. Read provided test steps
2. Read the key files directly with the Read tool (modules aggregator, test wrapper, main keys.dart, and the specific app feature files for the scenario). Do NOT use the Explore agent for this — these are known paths. Only use Explore when you genuinely don't know where something lives
3. Inspect existing modules for functions that can be reused
4. Also think if one of existing functions can be adjusted to match its existing usage and new test
5. Assign test keys to required elements if they are not assigned yet
6. Start writing test: reuse existing modules/functions + put new test steps in new test file
7. Write patrol actions directly in the test file, do not create new methods in modules
8. Run the test frequently during development — don't wait until the full test is written. Run after completing each logical group of steps to catch failures early
9. After full test passes, reorganize new code into existing/new modules. This is mandatory — the test file must only call module methods, not use Patrol APIs directly
10. Rerun the test after reorganizing to confirm it still passes

Patrol MCP Usage

When working with Patrol tests: