Hot answers tagged specflow
In my experience, you can't sell new development processes. The only path I've found which works is to simply start doing it: Only develop with TDD from this point forward. You'll still deliver your code on time, but it'll be more maintainable and have far fewer bugs. You'll feel much less anxiety and be proud of your work. After a little time, management ...
Although the technical answer to your question is no, there are some methods which help you limit the number of scenarios you need to cover to provide suitable coverage. I particularly like the Pairwise methodology Luckily there is a (no longer free) tool called Hexawise that helps you make sense of it without a mathematics degree! A particularly simple ...
I use Spinach and write tests in Ruby but I face the same issues when writing my tests - looks like managing page object context across the steps is a common problem when using Cucumber-like BDD frameworks. I think one can hardly find a perfect and universal solution for this one. All of them have their pros and cons. I tried several approaches (the code ...
I found out that you can filter tests in the Default.srprofile, for example <Filter>@myTag</Filter> will only run tests with the tag @myTag. More info is provided here: http://www.specflow.org/media/specrun.html#US18
I was able to fix this by adding stopAfterFailures="-1" to the Execution node in default.srprofile: <Execution retryFor="None" testThreadCount="1" testSchedulingMode="Sequential" stopAfterFailures="-1" />
Only top voted, non community-wiki answers of a minimum length are eligible