Scenario Outline, Nunit Test Names #214
Closed
infinitejest69
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
This is not something that we can control unfortunately. For scenario outlines (by default, see below) we generate data-driven tests with the Maybe you can try the NUnit config parameter DefaultTestNamePattern or some other config for NUnit in runsettings files. With Reqnroll the only thing you can do to force generating individual test methods for scenario outline examples by setting the Does that help? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This is not really a bug but a little bit of an issue i am experiencing that i could use help with.
i am using reqnroll after switching from specflow.
i am moving my tests in azure devops pipeline from windows to linux agents. ( for Mutiple reasons)
i was using the vstest task to automatically slice the tests over Mutiple agents. that task is not available on the linux agents. so i am manually slicing them based on this document
my issue seems to be when slicing tests up to run by name the nunit generated name for scenario outlines looks a little bit like the below with brackets and spaces as as opposed to a single string
when running
dotnet test --no-build --list-tests
imagine the above but on a much large scale with over 2000 tests. i need some way to make the scenario outline tests into a nice single string like normal scenarios either in code generation renroll change or some other way .
the dotnet test with filter Name= does not like spaces and all the other characters to escape.
open to ideas thought i would post here incase other have solved this issue with scenario outline names or a way to change how they generate
Beta Was this translation helpful? Give feedback.
All reactions