Automations

Open Automations to manage scheduled or run-triggered work, GitHub workflows, and suggested updates to your test instructions.

A tour of Automations: the New automation chooser, a scheduled Run tests automation from trigger to Save, pausing and Run now with its Run history, the Adapt test features GitHub workflow, and a suggested feature update reviewed and accepted.

Choose an automation

Choose New automation above the list. The chooser separates work that runs In TestVibe from workflows that run From GitHub.

Under In TestVibe, choose Run tests, Run a load test, Ask the Assistant, or Create an issue. Under From GitHub, choose one of the GitHub workflow templates.

Create an automation

1. Choose an action under In TestVibe, then enter a name.
2. Under Trigger, choose On a schedule or When a run finishes.
3. For a schedule, choose How often and Timezone. For a run event, use Only when to select any result, passed, or failed.
4. Under Action, configure the chosen work:
   • Run tests: use Choose tests or Change, select the tests or folders, then choose Done. An empty selection means All runnable tests. Expand Advanced options to review the environment, configuration, and optional failure analysis.
   • Run a load test: choose a saved load test and review its target.
   • Ask the Assistant: enter a prompt and review the available options.
   • Create an issue: choose a connected tracker and target. This action requires When a run finishes, because it describes that run.
5. Review Enabled under Status, then choose Save.

A test action dispatches its selected tests together as one run. Assistant jobs and issue actions have their own outcomes; not every action produces a browser run. Assistant work, including optional failure analysis, uses credits.

Review and manage

Turning Enabled off and choosing Save pauses the automation's scheduled and run-event triggers. The list then shows Paused. Pausing does not cancel work that is already running.

Open a saved automation's … menu and choose Run now to execute its action immediately. Review its target first. Check Run history and its result links after a firing; a dispatch is not proof that the resulting test run passed.

Run notifications follow your notification preferences. Email is the supported delivery channel; Slack, Google Chat, and Teams notification channels are not available.

GitHub workflows

Workflow setup lives in Automations. You can also reach it through Application → Set up automation. Connect the application's GitHub repository under Settings → Repositories → Application code; setup needs repository write access. These templates target GitHub Actions, even when other source providers are available elsewhere in TestVibe.

Choose New automation, then a template under From GitHub:

• On code changes runs tests for pushes to the default branch, pull requests, or both.
• On a schedule creates a daily workflow at the UTC time you choose.
• Adapt test features asks the Assistant to suggest updates to existing feature instructions when application code changes. Feature adaptation requires hosted TestVibe.

Choose All tests, Groups, Individual tests, or Smart tests. Run workflows need runnable generated tests. Smart tests uses AI to select tests related to each code change and skips a change when none match; that analysis uses credits. The daily schedule does not offer Smart tests.

Choose Create setup pull request, inspect the proposed workflow in GitHub, and merge the pull request when ready. Setup also stores a repository API key as a GitHub Actions secret. The workflow becomes enabled after merge; opening its setup editor alone does not run tests. Saved workflows appear under From GitHub, with their setup status and links to the workflow or open pull request.

The Enabled switch for a TestVibe automation does not control GitHub Actions workflows. Manage the generated workflow and its triggers in GitHub, or open its setup entry to propose configuration changes.

Adapt and review feature instructions

In Adapt test features, select the events and tests to review, then choose how to handle updates:

• Review changes holds suggested changes for approval in TestVibe.
• Auto-accept changes applies eligible updates after the background review completes successfully. Each update must pass validation and still match the feature revision it was based on. A failed review leaves suggestions unapplied.

Adaptation reviews up to 20 features per change. For larger projects, choose Smart tests or a smaller explicit scope. This workflow updates authored feature instructions; updated features need regeneration before their next code run.

Open Automations → Feature updates and expand a suggestion to compare Original feature with Suggested update. Read the validation message and confirm the change still describes the intended behavior. Choose Accept update to apply an eligible suggestion, or Dismiss to leave the feature unchanged. Accept is unavailable for invalid suggestions or when the feature has changed since the suggestion was created; a fresh update is needed for that conflict.

A suggested or accepted edit is not a passing test result. Review the saved instructions, regenerate their code, and run the test to verify the application behavior.

See Schedule runs, Run a group, and Application.