Why might my tests be being 'Skipped'? #522
-
Hi all. We are in the process of migrating from Specflow to Reqnroll. When I run things locally, from command line or using Rider IDE, everything seems fine and all tests run. When we run in our build CI pipeline, a number of tests are being 'skipped'. We are trying to work out why this is happening (may not be Reqnroll, but it's all started happening at the same time which is suspicious) Is there any way we can get dotnet test to tell us why tests were 'skipped'? Additionally - why would the 'Skipped' tests not be being counted under the number of Skipped tests listed at the end of the run (are there different skipping mechanisms?) - "Skipped: 0" Each of the feature files has an '@regression' tag at the top of the feature file which maps to the "TestCategory=regression" (NUnit). The command like that kicks off the test run in the build pipeline is: Example output with some of the skipped tests removed for brevity - a total of 16 tests were listed as 'Skipped', but then the Skipped count at the end is 0.
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Have worked it out. It's old step definitions that were regexes not being found. I'd not added the ^ & to the start and end of the string that is required. |
Beta Was this translation helpful? Give feedback.
Have worked it out. It's old step definitions that were regexes not being found. I'd not added the ^ & to the start and end of the string that is required.
Now to try and work out where the nice error messages went and why they didn't show up in the summary! Possibly that logging option.