Is there a way to show a warning or error in Visual Studio when there's a missing binding for a step?
I'm using the SpecFlow extension in Visual Studio 2022 with our C# selenium test suite. There are times when we have multiple .feature files using the same step definition methods (it's not really within my power or possible with any amount of time I have to go back and rewrite our massive test suite to change this). Every now and then someone will update the way a step is worded to use it in a particular scenario, and it will end up breaking steps in other untouched feature files. Is there a way to show a warning or a build error (perhaps when the feature.cs files are generated/re-generated) when that happens so we can see right away when a binding is broken instead of having to wait till we're halfway through our big selenium pipeline runs?
Please sign in to leave a comment.