Go To Definition (F12) is not working when step definitions are used from a different assembly. Is there a way to make it work?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Go To Definition (F12) is not working when step definitions are used from a different assembly. Is there a way to make it work?
This could be a bug or something like that in Specflow. I have the exact same problem. When trying to go to the Step Definition from the feature file, Visual Studio says there’s no matching step binding. Although, when trying to run the test(s), they run like they should, so Specflow can indeed find (and use) the matching step definitions.