CODEWITHSUNDEEP
c#mstestspecflow
Splateaux
Splateaux

Reputation: 11

No matching step definition found for the step when combining with normal mstests

We have developed a framework for writing unit and integration tests against our application which handles a lot of our basics like automatically cleaning up after itself and such. When we started writing SpecFlow tests against the same application, we extended our previous framework so that we wouldn't have to reinvent the wheel.

This works great... normally. What we've found is that when we run large groups of these tests together (combining both normal MSTests and SpecFlow generated tests), sometimes the SpecFlow tests will fail with the, "No matching step definition found." errors.

I can run any of the above tests individually, and they work fine. I can even grab chunks of the tests, and they'll work fine. Side note: Running all these tests together with debugger attached doesn’t cause the failure to happen.

Upvotes: 0

Views: 247

Answers (1)

Splateaux
Splateaux

Reputation: 11

A handful of our tests were messing with the appconfig like so:

AppConfig.Change("SomeTestConfig.config");

This was messing up SpecFlow such that it couldn't find the additional assemblies to load bindings from.

Upvotes: 1

Related Questions