If you encounter problems using SpecFlow or have any questions, one of the best places to turn for help is the SpecFlow Community page.
If you have found a bug, please first search the SpecFlow issues on GitHub to check that this is not already a known issue. If you cannot find a matching issue on GitHub, please submit a GitHub issue including as much information and context as possible, and ideally a code sample that allows the issue to be reproduced. The easier you make it for contributors to diagnose and fix your issue, the more likely you are to see results.
Please include the following information when submitting a bug report:
- Your SpecFlow version
- The test runner and version number you are using, as well as information on how you are executing the tests (e.g. include your command line)
- Your Visual Studio version
- Your .NET framework version
- A link to a project that reproduces the issue, if possible
Once you have submitted an issue relating to a bug, a contributor needs to take on the issue and provide a pull request containing a fix. Depending on the nature of your issue, how well it is described and how easy it is to reproduce, a fix may be delivered quickly or take a long time. You are actively encouraged to contribute and doing so can significantly reduce the time needed to fix issues that impact on your work with SpecFlow.