Why trigger tests from CI rather than from the ACCELQ interface?

Running from CI ties tests to code changes and releases. Builds can start tests automatically, and a failing run can stop a deployment.

What should go in a smoke suite versus a regression suite?

A smoke suite is small and fast and checks that the most critical flows work after every change. A regression suite is broader and runs less often, such as nightly.

ACCELQ Test Execution, Reporting, and CI/CD Integration

Introduction

Automation delivers value when it runs routinely and its results are easy to act on. This final ACCELQ lesson covers running Scenarios and Test Suites, scheduling them, handing execution to a CI pipeline, and making use of the results.

Prerequisites

Scenarios and Test Suites built in ACCELQ
Access to a CI tool such as Jenkins if you want to try integration

Step-by-Step Guide

Step 1: Run a Scenario or a Test Suite

A run can target a single Scenario or a whole Test Suite, which is a collection of Scenarios. Run a Scenario while you are building it, and a Suite for a broader check such as a regression or smoke pack.

Step 2: Choose when to run

ACCELQ supports running immediately, scheduling a run for a later time, and recurring runs. Scheduled times are interpreted in the timezone of the person starting the run, so check this when teams work across regions.

Step 3: Understand queuing and agents

Runs execute on an agent or execution host. If an agent reaches its concurrency limit, additional jobs wait in a queue, so plan capacity when you schedule many runs at once.

Step 4: Hand execution to your CI tool

ACCELQ can create a CI job so that the execution is triggered and managed by your CI platform, with integrations documented for tools such as Jenkins, Bamboo, and TeamCity. The general pattern is to create the job in ACCELQ, then configure the CI plugin with your ACCELQ details so a pipeline stage can start the run.

Step 5: Use results effectively

Review failures with the run report, separate real defects from flaky or environment problems, and track trends over time. Verify the exact Jenkins plugin configuration and options in the current ACCELQ support article before setting up your pipeline, since details change between versions.

FAQs

Why trigger tests from CI rather than from the ACCELQ interface?: Running from CI ties tests to code changes and releases. Builds can start tests automatically, and a failing run can stop a deployment.
What should go in a smoke suite versus a regression suite?: A smoke suite is small and fast and checks that the most critical flows work after every change. A regression suite is broader and runs less often, such as nightly.

Summary

Organize Scenarios into Test Suites, run them on demand, on schedules, or from CI, and keep an eye on agent capacity. Confirm integration specifics against the current ACCELQ documentation for your version.