Run a Scenario for Available CSV Entries

Run a Scenario for Available CSV Entries

BelowWhen area Scenario Editor test uses CSV-backed data, align the stepsexecution tocount be following in Scenario Editor.

Choose Scenario Type to be Performance Test

Choosewith the Resourcesavailable rows so the run does not reuse, skip, or exhaust data unexpectedly.

Recommended setup

• Confirm the CSV contains only valid rows intended for the execution.
• Document whether the header row is excluded from the resourcesdata >count.
• Decide DPLwhether data

  Definerows yourshould be consumed once, reused, or reset between runs.

• Keep sensitive data out of CSV files unless the storage and retention process is approved.

Validation workflow

1. Run with a small CSV sample and confirm row consumption behavior.
2. Review output to verify the expected row was used by each iteration.
3. Set the scenario execution count to match the intended number of available data entries.
4. Archive or reset test casesdata andaccording assignto the definedenvironment’s DPL.data policy.

From Test Management, Choose Completion Type to be “Conditional”

Choose the defined DPL and Condition to be “hasMoreData”