For the complete documentation index, see llms.txt. This page is also available as Markdown.

Generate test cases

Create grounded test coverage with the Author Agent.

Mozark's Author Agent writes test cases grounded in your app—its screenshots, PRDs, and user stories—rather than generic templates.

How it works

Your prompt ──► Knowledge base lookup ──► Author Agent ──► Review in chat ──► Save to TCM
                (screenshots, docs)       (generate)                          (with AI tag)

Walkthrough

1

Ask for what you want

"Generate test cases for the password-reset journey."

2

Answer three quick questions

The assistant always asks these—it never guesses them:

Question
Options

Knowledge base

Use existing content, or upload new screenshots/documents first

Test type

Functional · Edge · Automation

Polarity

Positive · Negative · Both

You can pre-empt the questions by putting everything in one prompt:

"Using the existing knowledge base, generate negative edge test cases for password reset."

3

The assistant checks context

It searches the knowledge base for your feature (retrieve_from_knowledge_base).

  • ✅ Found context for password reset — generation proceeds.

  • ⚠️ No context found — you'll be advised to upload screenshots or a document first. You can still proceed, but results will be more generic.

4

Review the draft

Generated cases appear in chat with title, preconditions, numbered steps, and expected results. Ask for changes freely:

"Make step 3 more specific about the OTP timeout."

"Drop the last two, they duplicate TC-41."

5

Save—only when you say so

"Save these to the Auth folder."

The assistant calls save_test_cases, which writes them to TCM and tags them as AI-generated, then embeds them for semantic search.

Nothing is written to your project until you explicitly ask to save.

Tips for better output

  • Feed the knowledge base first. Two or three screenshots of the flow plus the relevant PRD section make a large difference. See Build your knowledge base.

  • Name the feature the way your team does. Retrieval is semantic, but matching your own terminology ("Checkout v2", "Guest login") helps.

generate_test_cases · save_test_cases · retrieve_from_knowledge_base · get_skill_instructions · search_test_cases · embed_test_cases

Last updated

Was this helpful?