Release Notes - October 2026
What's new
Workflows let you define sequences of BearQ steps and run them as a single automated pipeline. Chain steps together, add conditional logic based on test results, and trigger the entire sequence on a schedule, from a CI/CD pipeline, from a coding agent via MCP, or on demand from the BearQ UI. BearQ includes pre-built default workflows, and you can create your own. 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.
Sources let you connect external tools to BearQ and use their content to drive test creation. Connect Jira, Zephyr, Reflect, or Swagger and BearQ syncs the content to the Sources page. From there, you can generate tests directly from individual items, link existing tests, or chat with the QA Lead agent in the context of a specific item. Each item moves through an inbox-style view so you can track what has been tested, what is in progress, and what you have chosen to skip.
BearQ tests now support Variables — dynamic values that control how a test runs at execution time. Every dynamic value in a test script is a variable with a default value. At runtime, you can override any variable with a specific value, leaving the rest to use their defaults. Variable overrides used in a run are visible on the task details page. This makes it possible to run the same test against different inputs, environments, or data without having to author separate tests.
Multi-step API flow tests
BearQ now generates multi-step API flow test cases that chain together multiple endpoint calls into a cohesive sequence, covering realistic end-to-end scenarios such as creating, modifying, and deleting a resource across multiple requests. BearQ also authors API steps from a plain-language description, detecting when a test step refers to an API request and automatically generating the backing metadata.