QGen 2.0 User Guide
Overview
QGen 2.0 democratizes test case generation by helping you create comprehensive test scenarios from product screenshots, Figma designs, Jira tickets, GitHub issues, requirements, and descriptions. Using AI, QGen analyzes your inputs to identify key workflows, edge cases, and potential scenarios, helping you improve test coverage, reduce manual effort, and ensure critical test cases don’t get missed.
1. What is QGen
QGen is Pcloudy's AI test-generation agent. Give it a feature description, a screenshot, a Figma design, a GitHub issue, or a Jira ticket, and it walks through a four-stage pipeline to produce structured, execution-ready manual test cases you can review, refine, and export.
You'll find QGen on the Pcloudy dashboard, alongside Qpilot (automation) and Qverify (API testing), under "Qgen — Test Generation Agent".
2. Setting up your workspace
Before generating test cases, set up a place to keep them:
- Create a Project — a container for all your testing work (e.g. one per product area).
- Create Folders inside the project to organize tests by feature or module.
- Create a Test Case inside a folder — this opens the conversation where you describe or attach your requirement.
Tip: You only need to do this setup once per product area — after that, keep adding test cases into the same project/folder structure.
3. The four-stage pipeline
Every requirement you give QGen — however you provide it — goes through the same four stages, shown as a progress bar at the top of the screen (WSF → CFG → Scenarios → Test Cases):
| Stage | Name | What QGen 2.0 Produces |
|---|---|---|
| 1 | WSF - Workflow Steps | A numbered, step-by-step description of the user journey QGen understood from your input, split into Main flow, Alternate flows, and Exception flows. |
| 2 | CFG - Control Flow Diagram | A visual flowchart of every path the workflow can take (decisions, branches, retries), so you can see the full shape of what will be tested. |
| 3 | Scenarios | A list of distinct test scenarios (happy path, edge cases, failures) that together cover the branches in the CFG. You choose how many and which ones to keep. |
| 4 | Test Cases | Execution-ready manual test cases for each selected scenario — preconditions, structured input data, and numbered steps with expected results. |
Each stage streams into the artifacts panel on the right as it completes, and a green checkmark marks a finished stage.
4. Starting a conversation: supported input types
Click the + icon in the message box to attach a source, or simply type a description. QGen supports:
| Source | How to attach it | Notes |
|---|---|---|
| Typed Description | Type directly into the message box, e.g. "generate test cases for password reset". | Fastest way to start; QGen will ask clarifying questions. |
| Screenshot/Image | Click the + icon → Add photos & files, or drag an image into the message box. | Good for UI-driven flows; you can attach more than one image. |
| Figma | Click + → Figma, then paste the Figma file URL and (optionally) an access token for private files → Load frames. | Imports the selected frame(s) as visual input. |
| GitHub | Click + → GitHub, then type or paste the issue URL URL after the inserted "/github" command, e.g. /github https://github.com/org/repo/issues/2 | Works for public issues; private repos may need a token — ask your admin if access fails. |
| Jira | Click + → Jira, then type or paste the ticket URL after the inserted "/jira" command, e.g. /jira https://yourorg.atlassian.net/browse/BA-1 | Jira must show as Connected under Pcloudy → Integrations first. If you get a connection error, simply retry the same command once. |
Tip: You can combine a typed instruction with an attachment in the same message, e.g. attach a screenshot and type "generate test cases for uploaded image".
Note: For JIRA and Github -Navigate to Integration page and establish the connection first
5. Answering QGen's questions
After you provide a requirement, QGen asks a series of questions to scope the work before generating anything. These appear as part of the conversation, and you always have three options available: continue, review, or revise.
| When QGen asks for | You can reply with |
|---|---|
| Which decision points / preconditions to cover | Numbers referencing the list (e.g. "preconditions 1", "decisions 1, 3"), the word "all" to cover everything, or "skip" to move on (skip also covers everything by default). |
| A lettered multiple-choice question (e.g. persona) | A single letter, e.g. "E" for "Cover all of it". Leaving it blank lets QGen pick the most relevant option. |
| How many scenarios/test cases you want | A number and, optionally, what to emphasize — e.g. "generate 10 scenarios, 2 test cases each, focus on things going wrong". |
| Whether to proceed | continue (move to the next stage), review (see the details again), or revise (ask for a specific change, e.g. "rename the workflow" or "add a timeout route"). |
Tip: If you're not sure what to answer, replying "all" or "skip" is always safe — QGen will cover the full scope rather than narrow it down.
6. Reviewing the workflow (WSF) and control flow graph (CFG)
Once QGen understands your requirement, it shows the Workflow Steps (WSF) — the main flow, plus any alternate and exception flows — as a numbered list. Review this to confirm QGen understood the feature correctly.
Next, it builds the Control Flow Graph (CFG): a visual diagram of every path the workflow can take, including decision points and failure branches. Use this to sanity-check that nothing important is missing before scenarios are generated.
Known issue: On workflows with a large number of steps, the CFG diagram can sometimes fail to render (the panel shows a node count but the canvas appears blank). If this happens, try opening it in fullscreen, or continue on to Scenarios and Test Cases — generation is not blocked by this, only the visual preview.
7. Choosing scenarios
QGen proposes a set of scenarios that together cover every branch of the CFG (it tells you how many branches are covered, e.g. "32 of 32 branches"). In the Scenarios panel you can:
- Check or uncheck individual scenarios to include or exclude them.
- Use Select All / Deselect All for quick bulk changes.
- Edit, duplicate, or delete a scenario before generating test cases.
When you're happy with the selection, click Generate Test (N) to move to the final stage.
8. Understanding a generated test case
Each test case includes:
- A unique ID (TC-001, TC-002, ...) and a priority tag (High / Medium).
- A one-line objective describing what the test verifies.
- Preconditions — the state the system must be in before the test starts.
- A structured Field / Value / Type table showing the exact input data to use.
- A numbered Step / Expected table with the precise actions and expected outcomes.
Tip: Test cases inherit the platform/tone (web vs. mobile) from the original requirement. If you notice a mismatch — for example steps say "Tap" for a workflow you described using "Click" — flag it for correction using Refine (see below) or report it via Revise.
9. Refining after generation
Once test cases are generated, use the Refine box above the results to make targeted changes without starting over — for example:
- "add a negative case for an expired session"
- "change TC-002's priority to High"
- "add a boundary test for the 3-request rate limit"
Type your instruction and click Apply.
10. Exporting your test cases
Click Export above the generated test cases and choose Download as CSV to save them outside QGen — for example, to import into your test management tool.
11. Frequently asked questions
QGen says it can't connect to Jira,Github— what do I do?
Go to Integration page and look for JIRA /Github and click on connect to establish the connection.
The CFG diagram looks empty — did something break?
Not necessarily. This is a known display issue on larger workflows (see Section 6). Your scenarios and test cases will still generate correctly — try fullscreen, or continue to the next stage.
Can I attach more than one source at once?
Yes — for example, you can attach two Figma frames, or a screenshot plus a typed instruction, in the same message.
What if I don't know how to answer one of QGen's questions?
Reply "skip" or "all" — QGen will default to covering the full scope rather than guessing narrowly.
Did this page help you?