You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The console output from MsTest is marking tests that have successfully passed as being skipped when this is not the case. The issue seems to be caused by the fact that if a scenario name has a special character such as forward slash "/" then the test is marked as skipped. This should not be happening as tests that have executed perfectly fine and passed should be marked as "Passed". This was working perfectly fine on Specflow.MsTest but due to having to migrate to Reqnroll.MsTest this issue has been discovered.
This was discovered when you run tests in the CI/CD workflow on GitHub actions.
See attached screenshot
.
Steps to Reproduce
Create a test that has a scenario name that contains a special character such as forward slash "/"
Configure and run tests in GitHub actions using MsTest
Observe the console output from github actions logs
Link to Repro Project
No response
The text was updated successfully, but these errors were encountered:
Reqnroll Version
2.2.1
Which test runner are you using?
MSTest
Test Runner Version Number
3.7.1
.NET Implementation
.NET 8.0
Test Execution Method
Other – PLEASE SPECIFY
Content of reqnroll.json configuration file
No response
Issue Description
The console output from MsTest is marking tests that have successfully passed as being skipped when this is not the case. The issue seems to be caused by the fact that if a scenario name has a special character such as forward slash "/" then the test is marked as skipped. This should not be happening as tests that have executed perfectly fine and passed should be marked as "Passed". This was working perfectly fine on Specflow.MsTest but due to having to migrate to Reqnroll.MsTest this issue has been discovered.
This was discovered when you run tests in the CI/CD workflow on GitHub actions.
See attached screenshot
.
Steps to Reproduce
Link to Repro Project
No response
The text was updated successfully, but these errors were encountered: