Understanding Scenarios Not Eligible for Data-Driving

A Scenario is data-driven when at least one of its parameters sources values from Test Cases. When no parameter does, the Scenario is not eligible for data-driving: it runs as a single non data-driven test, and ACCELQ maintains one system-generated Default Test Case for it.

When a Scenario is not eligible

Two situations produce this state:

No parameters at all. The Scenario's steps require no external input, either because the Actions define no input parameters or because values are fixed inside the Action logic. Example: a Guest User Verification Scenario whose steps invoke the browser with a hardcoded URL and verify static page content.

Every parameter configured with a non-Test-Case source. The Scenario has parameters, but each one is configured as a Literal Value, Global Property, Run Property (supplied at kickoff or passed from a previous test case in a Suite), or Linked Parameter. With no parameter left for Test Cases to control, there is nothing to data-drive. See Configuring Parameter Sources in a Scenario for these sources.

A non data-driven Scenario is often perfectly legitimate: smoke checks, static content verifications, and orchestration flows whose data comes entirely from properties or preceding steps have no business data to vary. Treat the state as a signal to pause only when the Scenario was meant to cover data permutations; in that case, review the configuration and return the business-varying parameters to From Test Case.

The Default Test Case

With no data variations possible, one Test Case is enough to represent the Scenario's execution:

• It is created by the system; you do not add it and cannot add others.
• It is the entity you select when adding the Scenario to a Test Suite.
• The grid shows this single Test Case row without parameter data columns, along with the message "Scenario is Not Eligible for Data-Driving. All step parameters in the business process use non-test case sources (overridden)."
• Metadata remains fully editable in the grid by double-clicking a cell: Custom Fields defined in Project Administration, such as Test Type or Priority, and Tags for filtering and regression suite planning.
• Execution works normally; running the Scenario runs this single test.

Entering and leaving this state

The state follows directly from the parameter configuration:

• If updating the configuration leaves no parameter on From Test Case, ACCELQ warns that all Test Cases will be deleted and the Scenario becomes a single non data-driven test, and asks for explicit acknowledgment before applying.
• To make the Scenario data-driven again, change at least one parameter back to From Test Case in the Input Parameter Configuration panel, then add values for it in the Test Cases grid.

Related articles

• Configuring Parameter Sources in a Scenario
• Working with Test Cases in ACCELQ
• Concept of Parameterization and Test Cases