From 6631cb6bbbfc23427826f67fec0d27270d8de154 Mon Sep 17 00:00:00 2001 From: John Gluck Date: Wed, 20 May 2026 13:31:43 -0700 Subject: [PATCH] Changing language to change implications of Automate --- qawolf/getting-the-most-out-of-mapping.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/qawolf/getting-the-most-out-of-mapping.mdx b/qawolf/getting-the-most-out-of-mapping.mdx index a5bb7ff..d39acc0 100644 --- a/qawolf/getting-the-most-out-of-mapping.mdx +++ b/qawolf/getting-the-most-out-of-mapping.mdx @@ -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. A common pattern: run Mapping to generate a broad outline, then use Automate to build out the flows that need more precision. - \ No newline at end of file +