Why separate data from logic?

One Scenario can then cover many cases, and adding a new case means adding data rather than building another test. It also keeps maintenance in one place.

Where should I check exact parameter options?

In the ACCELQ support documentation for your version, since the available data options and how they are presented can change between releases.

Data-Driven Testing and Parameters in ACCELQ

Introduction

Real applications need to be tested with many inputs: valid and invalid values, different users, different regions. Data-driven testing keeps the logic in one place and varies the data. This lesson explains the approach in ACCELQ and the habits that keep data manageable.

Prerequisites

Reusable Actions and a working Scenario
The idea of test data and expected results

Step-by-Step Guide

Step 1: Understand how Scenarios and test cases relate

In ACCELQ a Scenario can contain one or more test cases, which is how data-driven execution is expressed: the same logic runs once for each data set. A Test Suite is a collection of Scenarios.

Step 2: Parameterize instead of hard-coding

Replace fixed values in Actions with parameters, such as a username, search term, or expected message. The logic stays the same, and the data comes from the test case being run.

Step 3: Design a useful data set

Cover typical values, boundaries, invalid inputs, and special characters. Give each row a clear name that says what it proves, so a failed run points straight at the interesting case.

Step 4: Use execution parameters for environments

Keep environment-specific values, such as which environment to target, out of your Scenarios and supply them when the run is configured. This lets the same tests run against test, staging, and other environments.

Step 5: Keep data clean and independent

Do not let one test depend on data created by another. Use unique values or set up and clean up the data a test needs, so tests can run in any order and in parallel without interfering.

FAQs

Why separate data from logic?: One Scenario can then cover many cases, and adding a new case means adding data rather than building another test. It also keeps maintenance in one place.
Where should I check exact parameter options?: In the ACCELQ support documentation for your version, since the available data options and how they are presented can change between releases.

Summary

Keep logic in reusable Actions, supply values through parameters and test cases, and use execution parameters for environments. Independent, well-named data makes results easy to read and trust.