Migrate

Move from Behave Pro

Your scenarios, their links to Jira issues, your Git repository and your CI uploads all come along. Plan about 15 minutes for a project; both apps can run side by side while you check the result.

What moves, and how

In Behave Pro	In FeatureBridge
Scenarios on issues	Imported from Behave Pro's project export. Files go to the issue in their `@KEY` tag.
Git sync (GitHub, Bitbucket, GitLab)	Connect the same repository, branch and folder. Two-way sync works the same way: saves commit, pushes update the issue.
CI report uploads	`PUT` with `X-API-KEY` and `X-COMMIT-ID` is accepted as is. Change the URL and the key.
Test history	Not imported. Results start with your next CI run.

Before you start

Install FeatureBridge and turn on Show for all work items for the Scenarios panel. See Install and set up.
Keep Behave Pro installed until you have checked the import.
Have your Behave Pro API credentials (user and key) and the project ID at hand: they are in Behave Pro's project settings.

1. Export all features from Behave Pro

Behave Pro offers an export of all features of a project as a .zip file:

Terminal

curl --fail -u USER:API_KEY \
  "https://behave.pro/rest/cucumber/1.0/project/PROJECT_ID/features?manual=true" \
  --output features.zip

manual=true includes manual scenarios as well. Repeat for each Jira project you use Behave Pro in.

2. Import into FeatureBridge

Open Jira settings → Apps → FeatureBridge and scroll to Import scenarios.
Enter the Jira project key and choose features.zip.
Check the preview.
Behave Pro exports carry the issue key as a tag, so most files show ready. Files without a key are matched by the key in the file name or an issue with exactly the feature's name.
Click Import.

Issues that already have scenarios

They are skipped unless you tick Replace scenarios on issues that already have some. Nothing is overwritten by default.

3. Reconnect your Git repository

If Behave Pro synced with Git, connect the same repository, branch and folder in FeatureBridge (guides for GitHub, GitLab and Bitbucket). Then click Import from the repository to link the files that are already there.

One sync at a time

While both apps are connected to the same repository, both would commit on save. Disconnect Git in Behave Pro, or remove its webhook, before you connect FeatureBridge.

4. Switch your CI uploads

In FeatureBridge, create an upload key under Test results from CI and copy the upload URL. In your pipeline, replace the Behave Pro URL and key with these two values. The method and headers stay the same:

Before → after

# before
curl -X PUT -H "X-API-KEY: $BEHAVE_PRO_KEY" -H "X-COMMIT-ID: $GIT_COMMIT" \
  --data-binary @cucumber.json https://test-reports.behave.pro/REST/1.0/bdd/report

# after
curl -X PUT -H "X-API-KEY: $FEATUREBRIDGE_KEY" -H "X-COMMIT-ID: $GIT_COMMIT" \
  --data-binary @cucumber.json "$FEATUREBRIDGE_URL"

The next run shows ✓ / ✗ next to each scenario. See Upload CI results.

5. Check, then switch off Behave Pro

Open the project's Scenarios page: every feature should be listed with its scenario count.
Open a few issues and compare the scenarios with Behave Pro.
When you are happy, uninstall Behave Pro. Your scenarios in FeatureBridge and the files in Git stay.

Stuck?

Email support@yti.digital with the preview statuses you see. We help with migrations.

Behave Pro is a product of its respective owner; FeatureBridge is not affiliated with it.