Pre-setup

This guide assumes that you or your Jira administrator have installed the Behave Pro app in GitHub and have authorised the connect of Behave Pro to GitHub. If you haven’t, you can follow the steps of this guide to install and authorise Behave Pro (Note: Link to other guide)

Behave Pro project settings

To access the Behave Pro Git integration settings you need to access the settings menu for your the Jira project you want to work with. From there, locate ‘BDD Integration’ and click on it:

Once you click on the BDD integration option you will be presented with the start of the project setup wizard:

Configuring Behave Pro project settings

To begin the process of setting up your repository, click on the ‘Get Started’ button. This will take you to the second page of the wizard which gives you the option to select:

  • Classic workflow - Where feature files are stored with Jira and can be pulled via hooks into your automation architecture
  • GitHub workflow - Where feature files are stored within a GitHub repository of your choosing and any changes you make in the repository are reflected within Behave Pro.

Since we are setting up a Git integration, click ‘Get started’ in the GitHub workflow section.

  

Selecting the GitHub option will present us a form wizard to fill in to configure the project to connect to a specific repository. Here is a completed version of the form:

The form fields are broken down as follows:

  • Organisation - The organisation which your repository belongs to
  • Repository - The name of the repository that you want to connect to
  • Branch - The name of the branch you would like to save/ read the feature to/from
  • Repo directory - The folder in which you want to save the feature files in. This folder has to already exist. Behave Pro will not create the folder for you
  • Default test type - Determines whether new scenarios that are created are tagged with @manual or not

Once you have selected the repository you want to connect to, the branch and folder where the feature files will be stored and the default test type. Click on ‘Proceed’ to create the connection. Once completed you will be taken to the requirements page of your project where you can begin to create feature files and see them appear in your GitHub project.

Did this answer your question?