Skip to content

Removing tip for JSON block due to potential for confusion #131

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

Removing tip for JSON block due to potential for confusion #131

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
13 changes: 1 addition & 12 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 @@ -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

Expand Down Expand Up @@ -60,4 +49,4 @@ Mapping is designed for breadth — getting a full outline of an app's testable

<Tip>
A common pattern: run Mapping to generate a broad outline, then use Automate to build out the flows that need more precision.
</Tip>
</Tip>