Skip to content

PRD Upload & Test Generation

Overview

You can upload a Product Requirements Document (PRD) or provide an app description directly in the chat. VibeTesting uses this input to automatically generate relevant test flows for your application.

PRDs are stored per app URL, so you can maintain multiple PRDs at the same time — for example, one for staging and one for production, or separate PRDs for different products. When you run a test, VibeTesting uses the PRD that matches the URL under test.

A single chat message of app description or pasted PRD text is limited to about 10,000 words; longer input may be clamped on the server.

How it works

  1. Upload or describe — upload a PRD file or type an app description in the agent chat for the app URL you are testing
  2. Processing — the system processes your input to generate an app summary and may ask clarifying questions
  3. Review and approve — review the generated summary and confirm it reflects your application correctly
  4. Test generation — the platform proposes relevant test flows based on the approved summary
  5. Execute or save — the proposed flows can be executed as guided runs or saved as reusable Flow Goals

When you start a run against a URL, VibeTesting selects the PRD saved for that URL (if one exists) to inform test planning and generation.

PRDs per URL

Each app URL can have its own saved PRD. You can upload or update PRDs independently, so multiple URLs — and multiple PRDs — can coexist in your account.

  • One PRD per URL — upload or update the PRD for the URL you are working on
  • Multiple PRDs — keep separate PRDs for different apps, environments, or domains at the same time
  • Automatic selection — when a test run targets a URL, the PRD linked to that URL is used; other PRDs are not applied to that run

When you update a PRD for a URL, the system can regenerate or adjust the proposed test flows for that URL to reflect the changes.

Generated flows that become important repeat checks can be saved as Flow Goals and grouped into Flow Goal Suites for shared regression coverage.

When to use PRD upload

  • New projects — quickly generate a comprehensive set of test flows from your spec
  • Multiple apps or environments — maintain a separate PRD per URL (for example, staging vs. production)
  • Evolving apps — update the PRD for a URL as features change and regenerate tests
  • Teams without test plans — let the platform propose what to test based on your requirements