Skip to content

Flow Goals & Suites

Flow Goals

Flow Goals let teams save reusable, natural-language testing objectives for their application. Instead of rewriting the same guided test every time, you can define a goal once, store it in VibeTesting, and run it whenever you need validation.

A Flow Goal describes the user outcome VibeTesting should verify, such as:

  • Completing onboarding
  • Updating account settings
  • Checking a checkout path
  • Validating a critical regression area

Saved goals are managed under Inventory -> Flow Goals. Each saved goal can be triggered directly from Inventory, the External API, or the VibeTesting skill, using the app URL and configuration already verified in the dashboard.

Flow Goals are ideal for repeatable product checks, smoke tests, regression coverage, and agent-generated test plans that should become part of a shared QA inventory.

Flow Goal Suites

Flow Goal Suites let you group multiple saved Flow Goals into a reusable test collection. A suite can represent a smoke pack, release checklist, critical path coverage, onboarding validation, or any other set of flows your team wants to run together.

Flow Goal Suites are managed under Inventory -> Flow Goal Suites. Once created, a suite can be run by ID or name from Inventory, through the External API, or through the VibeTesting skill. The suite executes the selected saved goals with shared runtime options such as:

  • Login configuration
  • General instructions
  • Max steps per flow
  • Email reporting
  • Parallel execution

Together, Flow Goals and Flow Goal Suites make VibeTesting more repeatable: teams can move from one-off test prompts to a maintained library of user-centric validations that can be reused across releases, branches, and automated workflows.

When to use Flow Goals

Use Flow Goals when a test objective is worth keeping and re-running:

  • Smoke checks — confirm the product is basically healthy after a deploy
  • Regression coverage — preserve checks for areas that have broken before
  • Release validation — run critical paths before shipping
  • Shared QA inventory — keep important user journeys visible to the team
  • Skill-generated plans — turn agent-proposed flows from code changes into reusable saved goals

How they relate to guided runs

Flow Goals build on Guided Mode. A one-off guided run uses natural-language Tests Guidelines for a single execution. A saved Flow Goal keeps that objective under Inventory so it can be reused from the app, API, or skill.

Flow Goal Suites then group saved goals so teams can run a full collection together with shared settings.