Skip to content

Changing language to change implications of Automate #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
John Gluck (JohnGluck) merged 1 commit into from
May 20, 2026
Merged

Changing language to change implications of Automate #133

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions qawolf/getting-the-most-out-of-mapping.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,8 +56,8 @@ To use this: stop the AI, click through the flow yourself, and look for the **Ad

## Use Automate for flows that need more control

Mapping is designed for breadth — getting a full outline of an app's testable surface quickly. For flows that require precise setup (multi-step forms, specific dropdown sequences, dynamic file uploads), use [Automate](/qawolf/Automate-flows-using-AI-2d35b2a994fb8084b524cfc9aca7c358) instead. You can use Mapping to outline those flows and then automate them individually with more targeted prompts.
Mapping is designed for breadth — getting a full outline of an app's testable surface quickly. For flows that need individual attention, use [Automate](/qawolf/Automate-flows-using-AI-2d35b2a994fb8084b524cfc9aca7c358) to turn them into tests one at a time with more targeted prompts.

<Tip>
A common pattern: run Mapping to generate a broad outline, then use Automate to build out the flows that need more precision.
Comment thread
JohnGluck marked this conversation as resolved.
</Tip>
</Tip>