How to create a single method per scenario, rather than one method per GIVEN/WHEN/THEN/AND

[galabad71]

I would like to have reqnroll create only one single method per Scenario, rather than multiple methods. The reason for this is that when running in Azure Devops, I need to create multiple Azure Devops Test Cases because the Associated Automation can only link to one test. This becomes a problem when using tables, as I would need to create one DevOps Test Case for EACH row in the table. This is quite cumbersome. Also, I find having multiple methods per scenario to be a bit excessive and un-necessary, and a bit of a management headache when I have potentially hundreds of scenarios.

[gasparnagy]

You can set the generator/allowRowTests setting in the configuration to false and then a single method will be generated for each scenario outline example. See https://docs.reqnroll.net/latest/installation/configuration.html

(Self promo: you can also check SpecSync - a commercial tool to ensure that the scenarios and their results are in sync with Azure DevOps Test Cases.)

[galabad71]

Thanks for the reply. This suggestion still creates one test per row in the table, which will need one Azure DevOps Test Case for each row/test.

[gasparnagy]

@galabad71 ah sorry. I misread your question. You want the opposite.

That should be the default anyway. Which version of Reqnroll you use? Is it MsTest?

[galabad71]

My apologies for net describing the issue clearly. When "allowRowTests": true then Test Explorer in Visual Studio sets each row in a table to be a sub-test under the scenario.
When "allowRowTests": false, then each row is it's own test in Test Explorer (this is the image in previous comment).

either way (true or false), I still need to have one Azure DevOps Test Case per row in the scenario examples table. I cannot associate an Azure DevOps Test Case to the ScenarioOutline, I need to create one Azure DevOps Test Case for each row in the Examples table.

[gasparnagy]

There is no good solution for this. The azure devops test case association does not support data-driven test methods, but if there are individual methods for each example, you need many test cases. This test case association functionality is very limited.

[galabad71]

ok, thanks for your help on this.