Test Explorer when converting from Specflow+SpecRun to Reqnroll+MsTest using Gherkin #574
Unanswered
terrimitchell
asked this question in
SpecFlow migration Q&A
Replies: 2 comments 6 replies
-
Could you please post the generated test code with SpecFlow 3 and with Reqnroll 2? |
Beta Was this translation helpful? Give feedback.
5 replies
-
This is probably something else. There are unfortunately multiple issues with navigation in VS2022, especially with .NET framework. See reqnroll/Reqnroll.VisualStudio#75 These are hard to fix unfortunately |
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
in Specflow, Test Explorer matched the feature file Scenario text exactly.

But in Reqnroll, the Scenarios are converting all dashes and periods to underscores, as well as changing it to camel/Pascal case and removing all spaces. As a result, we can no longer double-click on a test or even choose the "Go to test" option when right-clicking. It is also much harder to read the test names now.

Is there some plugin we need to add or something to get Test Explorer to work like it did before and 1) NOT change the test name at all and 2) allow navigation to the feature file?
We were and still are using MSTest.TestAdapter and MSTest.TestFramework, though we were using an older version in Specflow (3.0.2) vs Reqnroll (3.8.3).
Beta Was this translation helpful? Give feedback.
All reactions