Test Suites in ACCELQ

A Test Suite in ACCELQ is a collection of Scenarios (and the Test Cases they encompass) that are grouped together for execution as a cohesive unit. Test Suites provide structure to test automation by allowing teams to organize, manage, and execute related test cases based on business needs, testing objectives, or development cycles.

Whether you’re conducting a focused Smoke test or a comprehensive Regression sweep, Test Suites help streamline execution across environments, ensuring your test coverage aligns with project goals.

Each Scenario in ACCELQ may contain one or more Test Cases, representing different data-driven variations of the same test logic. Suites can be configured not only to include specific Scenarios, but also to filter down to specific Test Cases for fine-tuned control over what executes.

1. Purpose and Role of Test Suites

Test Suites in ACCELQ serve as reusable, manageable groupings of Scenarios that facilitate:

• Functional Organization: Grouping Scenarios that validate specific application areas or workflows.

• Purpose-Driven Execution: Running Scenarios for specific goals such as Smoke, Sanity, or Regression testing.

• Reusable Execution Blocks: Reusing Suites across different sprints, releases, or execution environments.

⚠️ Important Note:
A Test Suite is not tied to a sprint or release directly. Instead, in a given sprint or release cycle, you may execute one or more Suites as part of your validation effort—possibly across different environments, browsers, or platforms using Execution Configurations.

2. Types of Test Suites

ACCELQ supports two primary types of Test Suites:

🔹 Static Test Suites

Static Suites are manually assembled by selecting Scenarios and arranging them in a defined order.

• Execution Order is Preserved: Scenarios run in the specified sequence.

• Ideal For: End-to-end workflows or processes where order matters (e.g., onboarding flows, checkout processes).

• Parallel Execution: Not supported in Static Suites, due to the dependency on execution order.

🔹 Dynamic Test Suites

Dynamic Test Suites in ACCELQ are built using flexible filter criteria that automatically include Scenarios matching the specified conditions. This enables adaptive, low-maintenance test organization aligned with evolving project needs.

• Self-Updating: The suite automatically includes or excludes Scenarios as their attributes change—no manual updates required.

• Flexible Filters: Define conditions using standard metadata fields like tags, application modules, scenario name, status, and more.

• Custom Field Filtering: Apply filters based on user-defined custom fields, such as priority, feature area, or business module, enabling powerful and context-specific test grouping.

• Traceability-Based Filtering: ACCELQ supports deep traceability—each Scenario can be linked to one or more requirements or user stories from external systems like Jira, Azure DevOps (TFS), Rally, and others. You can use these linked requirements as filter criteria in Dynamic Suites.

• Ideal For: Functional grouping (e.g., by module, feature, or risk level), as well as purpose-driven suites like Smoke, Sanity, or Regression.

• Parallel Execution: Supported, allowing high-performance execution across configurations and environments.

3. Creating a Test Suite in ACCELQ

▶️ Creating a Static Suite

1. In the top-navigation bar in ACCELQ, click “+ " and select "Test Suite”.

2. Select "Static" as the Suite Type.

3. Enter a meaningful name and (optionally) a description.

4. In the Test Suite page, click the link to select the Scenarios to include in the suite.

5. Arrange the scenarios in the desired execution order using the drag-and-drop interface.

6. Test Case Filtering: After selecting Scenarios, you can further refine which Test Cases (data rows or variations) should be included during execution. This allows you to focus the suite on specific data-driven conditions.

7. Save the suite.

Use Static Suites when the sequence of scenario execution is important and must be preserved exactly.

▶️ Creating a Dynamic Suite

1. In the top-navigation bar in ACCELQ, click “+ " and select "Test Suite”.
2. Select "Dynamic" as the Suite Type.
3. Enter a meaningful name and (optionally) a description.

4. In the Test Suite page, define filter conditions to automatically include matching Scenarios.

   • Examples of filter criteria:

     • Tag = smoke

     • Application Module = User Management

     • Status = Ready

     • Requirement ID contains USR-123

5. Test Case Filtering: In addition to filtering Scenarios, Dynamic Suites allow you to specify criteria to include only certain Test Cases, enabling targeted, data-driven suite execution even within a broader Scenario filter.

6. Save the suite.

As scenarios are added or updated in the workspace, this suite will automatically stay up to date.

4. Example Use Case: Smoke Testing with a Dynamic Suite

Let’s walk through a real-world example:

Objective: Run a quick health check of the application using all Scenarios tagged as "smoke" and marked high-priority.

Steps:

• Create a new Dynamic Suite.

• Define the filter:

  • Tag = smoke

  • Priority = High

• Optionally, filter by Module = Core API or Application = Web Portal.

• Name the suite: Smoke – Core Functionality.

• Save.

You now have a fully reusable, self-updating Smoke Suite ready to run anytime across any Execution Configuration.

Want to run only “Happy Path” test cases from Scenarios linked to critical requirements?
Define your Dynamic Suite by Requirement ID, then use the Test Case filter to include only rows where Test Type = Happy Path ("Test Type" is a custom field applied at the level of "Test Case" in your project configuration).

5. Executing a Test Suite

In ACCELQ, test execution can be initiated for:

• A single Scenario, or

• A full Test Suite.

To run a Suite:

1. Click “Run” button in the top-navigation bar.

2. Select "Test Suite" under "What to Run" and then select the suite by its name.

3. Choose the Execution Configuration, which may include:

   • Environment (e.g., Dev, QA, UAT)

   • Platform/OS

   • Browser

4. Launch the execution. 

6. Best Practices for Working with Test Suites

• ✅ Use Static Suites when test logic has hard sequencing or Scenario dependencies.

• ✅ Choose Dynamic Suites for modular, scalable test management and reduced maintenance overhead.

• ✅ Leverage Tags and Requirement IDs strategically to categorize and filter Scenarios.

• ✅ Keep Suite names descriptive and purpose-driven (e.g., Regression – Billing, Smoke – API, Sanity – Mobile UI).

• ✅ Avoid tying Suites to individual sprints. Instead, think of them as reusable testing assets supporting multiple cycles.

✅ Summary