Sync feature files

Use BDD sync when feature files are the source of truth for your scenarios. TestCollab holds the synchronized definitions and execution evidence; your Git repository owns the definitions.

Run the sync

From the Git repository containing your feature files:

export TESTCOLLAB_TOKEN='your-api-token'
tc sync --project 123

Use --api-url https://api-eu.testcollab.io for an EU account.

Understand ownership

Synced suites and cases carry BDD ownership markers. Edit scenario definitions in the feature files and sync again. Ordinary case writes must not be used to overwrite a definition owned by the repository.

When a synced scenario disappears, the sync can archive its case. A returning scenario is handled by the sync’s identity and revision rules. Do not create a second ordinary case to work around a missing or archived synced case.

Publish execution results

Run your BDD test runner, produce JUnit results, and use CI reporting. Keep scenario titles, feature context and case references stable enough for the result mapper to identify the intended case.

Scenario outlines produce multiple example results. Preserve that information in the result file so the execution history reflects the data rows that actually ran.

First rollout

Sync a small feature folder into a project where you can inspect the result. Review suite placement, scenario identity and a second sync before integrating the command into every pipeline.