Working with Test Cases in ACCELQ

In ACCELQ, Test Cases are data-driven instances of a Scenario. While a Scenario defines the logic and flow of steps, the Test Cases provide the actual data required to execute that flow.

The Test Case grid provides comprehensive capabilities to manage data variations, configure parameters, and execute tests. This article outlines the features and usage of the Test Case management interface.

The Test Case Grid Overview

When you navigate to the Test Cases tab within a Scenario, you are presented with a grid view structured for clarity:

• Rows: Each row represents a unique Test Case (data variation).

• Columns: Columns represent the parameters defined in the Scenario steps, as well as metadata like Custom Fields and Tags.

• Step Grouping: Parameters are visually grouped under the Step they belong to (e.g., Invoke Browser, Login to QBank, Transfer funds, etc.), making it easy to see exactly where data is injected into the flow.

Detailed View

To view a specific test case in isolation without the noise of the full grid, click the Test Case ID link. This opens a detailed modal view of that single test case's data.

Editing Test Case Data

To modify parameter values, Tags, or Custom Fields, you must switch the grid to Edit Mode.

Entering Edit Mode

There are two ways to activate Edit Mode:

1. Double-Click: Double-click on any data cell within the grid to instantly switch to Edit Mode and focus on that cell.

2. Edit Button: Click the Edit (pencil icon) button located in the toolbar above the grid.

Working in Edit Mode

Once Edit Mode is active, the interface focuses exclusively on data entry:

• Direct Editing: Click any cell to modify its value.

• Keyboard Navigation: Use the Tab key to move rapidly from one cell to the next, allowing for fast bulk updates.

• Interface Restrictions: To prevent conflicts, standard toolbar buttons (such as Run or Export) and Context Menu options are hidden while in Edit Mode.

• Save Changes: Updates are not permanent until confirmed. You must click Save Changes in the toolbar to commit your updates, or Discard to revert them.

⚠️ Restriction: Overridden Parameters

If a parameter has been Overridden at the Scenario step level (e.g., set to a fixed Static Value or Global Property, or linked with another parameter), the cells in that column will be read-only.

• These values are defined globally for the Scenario and cannot be altered at the individual Test Case level.

• To edit these values, you must click the configuration icon in the Parameter Header and change the configuration (as described in the next sections).

Renaming Test Cases

You can rename a test case quickly without entering the full "Edit Mode."

1. Click to Edit: In the standard grid view, simply click on the text in the Test Case Name column.

2. Confirm: An inline input field will appear with Tick (Confirm) and Cross (Cancel) icons.

3. Validation: Upon clicking the Tick mark, the system automatically validates the new name to ensure it is unique and follows naming conventions before saving.

Test Case Operations

Management operations are available only when you are not in Edit Mode.

Context Menu Actions

Hover over a test case row and click the Context Menu (three-dots icon) in the test case name column:

• Run Test Case: Execute only this specific data variation.

• Clone: Create a copy of the test case to quickly create a new variation with similar data.

• Delete: Remove the test case permanently.

Bulk Actions

You can select multiple checkboxes on the left side of the grid to perform actions on several test cases at once, such as Run (executing selected cases as a batch) or Delete.

Execution Status

The grid provides quick insight into execution health. The Last Run column displays a status indicator (e.g., Red for failure, Green for pass) along with the timestamp of the last execution. You can click this cell to navigate to the latest execution result report.

Configuring Parameters

By default, parameter values are data-driven, meaning you provide specific values for each row in the Test Case grid. However, for certain parameters (like a common URL or Admin credentials), you may want to use a fixed value across all test cases. This is achieved through Parameter Overriding.

To configure or override a parameter, click the configuration icon in the Parameter Header (column title) in the grid.

Available Configuration Options

• Test Case (Default): The parameter remains data-driven. You enter specific values for each test case in the grid rows.

• Static Value: Specify a fixed, literal value. This value will be used for every execution of this scenario, and the column in the grid becomes read-only.

• Global Property: Link the parameter to a Global Property. This allows you to centrally manage data (like Application URLs) that may vary across different environments (QA, Staging, Prod).

• Run Property: The value is not defined now but supplied when the test is actually kicked off (Runtime). This is useful for dynamic values like a "Password of the Day."

• Link with another Parameter: Connect the parameter to an Input or Output parameter from a preceding step in the Scenario. This is essential for passing data through a flow (e.g., using a generated Order ID from Step 2 as an input for Step 3).

⚠️ Important: When you change a parameter source from "Test Case" to an overriding source (like Static Value or Global Property), any existing data in the test case grid for this parameter will be lost. The parameter will now function strictly based on the override configuration.

Generating and Importing Test Cases

ACCELQ offers powerful tools to generate test cases automatically:

• Autopilot Generation: Use Generate > Autopilot to have AI automatically create relevant test cases based on your scenario's logic.

• Algorithmic Generation: If parameters are linked to Data Lists, you can generate test cases algorithmically (e.g., All Pairs, Combinations) to ensure optimal coverage.

• Excel Import/Export:

  • Import: Upload an Excel sheet to populate the test case grid with bulk data.

  • Export: Download your current test cases to Excel for offline review.

Special Display Modes

Compact View

When a Scenario contains a high volume of data (typically exceeding 100 Test Cases or Parameters), the grid automatically switches to Compact Mode. In this view, only the Test Case Name and Metadata (Tags/Custom Fields) are displayed to optimize performance and readability.

Non-Eligible Scenarios

If all parameters in a Scenario are overridden (meaning no parameters are left to be data-driven by the test case), the Scenario becomes ineligible for standard data driving.

In these instances:

1. The grid displays a message: "Scenario is Not Eligible for Data-Driving."

2. You cannot add new data rows/test cases.

3. However, you can still update the Metadata (Tags, Priorities, and Custom Fields) for the single system-generated test case visible in the grid.