From e3014dc870afc2939a6a5d9cd900db84b81460aa Mon Sep 17 00:00:00 2001 From: John Gluck Date: Wed, 20 May 2026 13:04:56 -0700 Subject: [PATCH] Removing tip for JSON block due to potential for confusion --- qawolf/getting-the-most-out-of-mapping.mdx | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/qawolf/getting-the-most-out-of-mapping.mdx b/qawolf/getting-the-most-out-of-mapping.mdx index a5bb7ff..c871d86 100644 --- a/qawolf/getting-the-most-out-of-mapping.mdx +++ b/qawolf/getting-the-most-out-of-mapping.mdx @@ -16,17 +16,6 @@ Mapping needs enough context to navigate your app and generate meaningful flows. - The application name (used to name the folder Mapping creates) - Any specific task or scope -Passing this as a JSON block makes it easier for Mapping to parse, though multiple sequential prompts work too. - -```text -{ - "url": "https://staging.yourapp.com/dashboard", - "email": "test-user@yourcompany.com", - "password": "your-password", - "application_name": "Your App", - "task": "Create a new folder called 'Your App' and outline the application." -} -``` ## Set a flow target @@ -60,4 +49,4 @@ Mapping is designed for breadth — getting a full outline of an app's testable 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 +