In the last weeks we have released updates for the latest version of our product. The releases 3.2.1 and 3.2.2 contain useful improvements and fixes for publishing test results, a new customization and other bug fixes. Please find the complete list of changes in the Changelog.

Details of the updates

After upgrading to this release, you will be able to see the step-level output messages (messages that have been printed to the output by step definitions) directly on the rest result detail page of Azure DevOps. This feature was available already with Cucumber JSON results, but now it has been improved further and it is also available for SpecFlow.

SpecSync now supports results from Jest (using the jest-cucumber package). With the “jestCucumberXml” format value, the Jest results can be directly published. (Please make sure you do not override the “titleTemplate” or the “classNameTemplate” settings in “jest.config.js”.)

With the support of Jest, SpecSync supports 13 BDD framework test result formats! Check the full list in the Compatibility page. Contact us if the one you use is not on the list yet.

Our new customization (named Reset Test Case state) helps supporting development processes where the Test Case can only be modified when it is in “Design” state, but changes from scenarios should be automatically approved (reset the state to “Ready”) if the scenario has a certain tag.

Hotfixes for v3.1

Following our versioning policy we still provide important bug fixes for the earlier releases. In this case the recently released update for v3.1 (v3.1.2) has been published. We always recommend upgrading to the latest updates of the release you use.

While fixes for v3.1 will be provided for a while, we recommend upgrading to v3.2 to get the benefits of our improved test result publishing features. Upgrading from v3.1 to v3.2 is a simple process for most of the cases, as we’ve only had a few minor breaking changes that you can check in the documentation.