-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cant Run Tests on Rider 2021.1.X #76
Comments
Could you check which test runner are you using for SpecFlow (e.g. Nunuit, Xunit, MSTest or SpecFlow+Runner)? |
Also be sure to build (or rebuild) the solution |
@deadmann are you still having issues with running the Tests? |
@nemesv yes I still have the issue after updating the plugin |
@deadmann can you share the project with us ? or can you reproduce this on a smaller project that you can share, it will help us identify the problem. |
Unfortunately I signed an agreement that I cant share resources.
This would be hard to spare free time as most of my day spend at work or the long way to and from home... so I wont give any promises, only if I found time, and also I remembered the matter. SpecFlow 3.7.3 |
@deadmann no other test framework means that you are using the SpecFlow+Runner. The SpecFlow+Runner currently is not supported testrunner by Rider in general. So running the tests is also not working in the SpecFlow for Rider plugin. |
Hey, @nemesv just want to check in - are there plans to support Specflow+Runner in the future? If no, is there somewhere I can request this issue? 😃 Thanks! |
@gavinroderick you can post feature requests here: https://support.specflow.org/hc/en-us/community/topics/360000519178-Feature-Requests |
Dear sir,
I recently update my rider, and after that I received a project which uses SpecFlow for its acceptance testing, and the issue I have is when I right click on the
Test Project
, the run test button is disabled, and when I go to test scenarios no green button appear beside tests... so it's not testable at all.The text was updated successfully, but these errors were encountered: