As announced last month, we started this year with our first Open- Source- Iteration. And you can already use the result of it. We released last week SpecFlow 3.6, which contains all the features and bugfixes from the two weeks of work.
During these two weeks, we merged in total 26 Pull Requests to the SpecFlow GitHub repository. This is the list:
- Update version number to 3.6-beta
- Update bug_report.md
- build Specs for correct TFMs depending on MSBuild Runtime
- Improve building (local + build servers)
- Update issue template to 3.6
- Change version to 3.6
- Fix duration in case of failed Step
- Docs: Executing specific Scenarios in your Build pipeline
- Document as known issue: Generating step definitions provides deprecated code
- Handle errors in BeforeScenarioHooks
- contribution guideline update
- Access Feature level tags in Scenario level via ScenarioAndFeatureTags
- Add documentation about how to write and use a Decorator
- Batch changes while a build is in progress
- Search for RuntimePlugins in the TestAssembly
- Correctly handle Table argument step transformations when multiple matching transformation exists
- Fix flaky test and netcoreapp2.1 Unit Test runs
- Documentation: Hook parameter injection
- Use latest .NET 5 SDK + Update submodules
- Docs: remove obsolete page
- Do not show generation error in case of empty feature file
- Remove warnings from source
- Be able to access MSTest TestContext in BeforeTestRun/AfterTestRun
- CI build should trigger only for master
- Fix parser tests
- Show duration for a failed step
We did also a lot of work to improve the build system of SpecFlow, to make it easier for new contributors to start working on SpecFlow!
And don’t forget, this was not a one- time event. We are already looking forward to the next OSS Iteration from 2021-04-06 to 2021-04-19.
In the meantime, if you want to start contributing to SpecFlow, join us on our Discord server!