Hi everyone,
I am facing a frustrating issue in Test Manager with data-driven testing, and it seems like a regression bug introduced in the recent Test Manager updates.
The Setup:
- I have a Test Case in Studio with an Excel file attached via “Add Test Data”. The Excel file has 10 rows of test data.
- The Test Case also has two manual input arguments (
inSecurityRolesandinCompany). - I am reusing this exact same Test Case across two different Test Sets (Test Set 1 and Test Set 2).
The Problem: When I run the Test Case normally, it works perfectly and executes 10 times (iterating through the 10 rows in my dataset).
However, I need Test Set 1 to use “Role A” and Test Set 2 to use “Role B”. To achieve this, I go to Test Manager → open the Test Set → select the Test Case → click Override parameters → and enter the specific value for inSecurityRoles (leaving the dataset-driven arguments blank).
As soon as I apply an override to any parameter, Test Manager completely ignores the attached Excel dataset. Instead of running 10 times, the execution triggers only 1 time, using the overridden value and leaving the rest of the dataset fields blank.
Constraints & Workarounds we’ve ruled out:
- Orchestrator Assets: I cannot replace the parameters with a
Get Assetactivity in Studio because both Test Sets run in the same Orchestrator folder. They would end up fetching the exact same asset value. - Duplicating the Test Case: I want to avoid the “brute force” method of duplicating the
.xamlfile in Studio just to attach two separate Excel files.
Before the recent updates to Test Manager, this worked exactly as intended (merging the dataset rows with the overridden parameter). Now, the override acts as a kill-switch for the dataset.
Is this a known bug being worked on? And does anyone have a clean workaround for passing Test Set-specific parameters to a data-driven test without breaking the dataset iteration?
This is writing by Gemini
Thanks in advance!