Behave Pro is compatible with the Gherkin family of test automation tools; Cucumber, Cucumber-JVM, Cucumber-JS, SpecFlow (C#/.net), Behat (PHP) and Behave (Python). These all consume plain text feature files in the Gherkin format and Behave Pro generates this format for BDD scenarios and features. For certain programming languages and projects type Behave Pro can even display test results within Jira.
There two different project types in Behave Pro:
- Classic - The original project type in Behave Pro where the data is stored inside Behave Pro and be exported by users or build tools to be executed as Automated tests
- Git connected - A new project type where feature files are stored in the team's Git repository and any change made in Behave Pro to features or scenarios are committed directly to the git repository. Any commits made by testers or developers are synced back into Behave Pro and Jira.
For most projects, we recommend using a Git connected repository as it has the latest features that benefit teams the most. An important feature difference is Git connected projects support publishing test results to Jira from Cucumber and SpecFlow.
Git connected project - Test Automation advice
With a Git connected project, the Gherkin feature files already live in your team's source code repository. Behave Pro allows you to configure, as part of the project configuration process, the directory where feature files are stored. If this location matches the expectation or configuration of your BDD tool of choice then no further work is required.
For team using Cucumber or SpecFlow with Behave Pro can take the configuration a step further to publish test results back into Jira. See how to configure Living Documentation to find out how to do this.
Classic Project - Exporting for Test Automation
You can integrate one of Behave Pro's build tools into your projects build process to export all the feature files for your project to a local directory before executing Cucumber or your preferred automation tool of choice.
Please see this guide for detailed instructions on using the export functionality for classic projects.
- Maven and Gradle plugins/tasks for teams using Cucumber-JVM
- MSBuild for teams using SpecFlow and Visual Studio
- Rake task or command line interface for teams workings with Cucumber Ruby
- NodeJS module for teams using Cucumber-JS
- Python library or command line interface for teams working in Python (Behave or Lettuce)