Workflows

Workflows let you define what QA work should happen and when, and BearQ runs it automatically. You can chain BearQ steps together, add conditional logic based on test results, and invoke the entire sequence in any of the following ways:

  • On a schedule you configure.

  • From a CI/CD pipeline, using the BearQ public API.

  • From a coding agent, using the BearQ MCP server.

  • From BearQ

Every run is logged step by step so you can review what happened at each stage. Workflows replace the Work page. All existing tasks and schedules are available from the Workflows page.

How Workflows work in BearQ

BearQ tasks, such as Expand Application Model and Expand Test Coverage, can be run individually. Workflows let you compose those tasks into a pipeline and run them in sequence.

BearQ includes pre-built default workflows. You can also create your own. You have to run a Workflow once before you can schedule it. This applies only to custom workflows. Before you add a time schedule or event trigger to a custom workflow, run the workflow to completion. A canceled run does not count. You can schedule a default workflow before you run it, but you cannot add event triggers to a default workflow.

A workflow consists of a series of steps, which are the units of work BearQ performs. Each step appears as a node in the workflow graph. Steps can be native BearQ tasks or tasks from connected integrations, such as creating a Jira issue or syncing results to Zephyr.

The Workflows page is the central place to manage all your workflows. From this page, you can do the following:

  • Create new workflows.

  • Run existing workflows on demand.

  • View schedule trends across all workflows.

  • Access default system workflows that come prebuilt with your workspace, alongside the workflows you create.

Default Workflows

Here are the default workflows:

  • Expand Application Model

  • Expand Test Coverage

  • Generate Summary Report

  • Rapid Discovery Mode

  • Run All Regression Tests

Publication date: