Why you should connect your BDD tool to Git

Ever since we first launched our Git connector in 2018, it has been having a profound impact on teams that use test automation with Cucumber or Specflow to turn their captured user story examples into executable specifications and create living documentation.

The popularity of early versions of our Git connector proved just how much value teams’ were getting out of using it, so we have been striving to continually improve, adding BitBucket and GitLab support alongside GitHub, and earlier this year adding support for Feature Branching to work with different teams branching strategies.

But why is it so popular? There are three main benefits to connecting Behave Pro with Git:

1) Two way synchronization means technical and non-technical members of the team can work together, separately

We’ve always been committed to making Behave Pro accessible to Product Owners, as we believe the true benefits of BDD can only be achieved with their involvement. However this accessibility for the Product Owner created an extra step for Developers and Testers, as they would have to export the Feature Files from Jira in order to run automated tests with Cucumber and Specflow and, if any changes were made, have to return to Jira to replicate the updates. Behave Pro’s Git connector ensures that all scenarios and features can be viewed & edited from both Jira and Git, and are always synchronized to prevent any misunderstandings.

2) A single source of truth for your requirements & code

If your requirements are stored separately from your code, you will need to pull down different versions of your requirements and match them with various versions of production and test code, leading to opportunities for errors. By connecting Behave Pro to your Git repository, all of your production code, test code and requirements all live in one place, minimising confusion and creating a single source of truth for what you are building. This means you can work being always safe in the knowledge that your requirements, features and scenarios will always match production code changes you are making.

3) Test results will always match the code changes you are testing

If you’re using a test management tool then your chosen tool is essentially creating another code repository just for your tests. This can lead to the same potential for error as mentioned above, as the tests may not always match the correct version of code changes that you are testing. If a team either doesn’t put the effort in to match them manually, or they don’t realise there is a discrepancy they may have false positives or false negatives that create rework further down the line. By connecting Behave Pro to your Git repository, your tests will always be located in the same repository as your requirements and production code, so you can be confident that your test results are giving you the true picture.

To get a demo of Behave Pro and our Git connector please book a meeting, or sign up for an evaluation on our marketplace listing.