Scenario Outlines sync as dataset-driven test cases, Cucumber results report back without IDs in your feature files, and a removed scenario is archived instead of deleted.
Teams that keep Gherkin feature files in Git and run
tc sync get a much closer match between the
.feature file and the test case in TestCollab, and the results of running those features now report straight back into the cases the sync created.
-
Scenario Outlines run once per example row - the
Examples: table becomes a test dataset linked to the case, and each
<placeholder> in the title and steps becomes
{{placeholder}}, so a test plan runs the outline once per row with a result per row. Test datasets need the Elite or Enterprise plan; on other plans the outline syncs as before and the sync summary says so.
-
CI results land on synced cases with no IDs in your feature files -
tc report matches a Cucumber JUnit result by its feature title and scenario title, the pair the sync stored, so a
.feature file needs no TestCollab ID marker. Scenario Outline rows roll up into one result per case, and
--auto-create no longer creates a second copy of a synced scenario.
-
A removed scenario is archived, not deleted - when a scenario leaves its feature file, its test case is archived and tagged
Removed from repository, with its revisions, runs and results intact. If the scenario comes back with the same steps, the next sync restores the same case. A deleted feature file archives its cases and keeps the suite.
-
Data tables and doc strings sync with their step - a step's table shows as a table and its text block as a preformatted block on the test case, and a Background table appears on every case of the feature.
-
Rule blocks and feature tags - scenarios under a
Rule: heading sync into the feature's suite, and tags on the
Feature: line apply to every case in the file. Tags no longer end up in case and suite descriptions.
-
Gherkin keywords in steps, if you want them - turn on
Show Gherkin Keywords in BDD Steps in the project's general settings and synced steps and expected results start with their Given, When, Then or And, so testers read a case the way it is written in the file.
tc sync --project 45
tc report --project 45 --test-plan-id 123 --format junit --result-file cucumber.xml
Also fixed: two scenarios with the same steps in one file keep their own test cases, a mandatory custom field no longer blocks the sync, the sync summary prints the real counts and warnings instead of "No changes were required", and the change log of a synced case shows the right user and the actual change. Update to the latest tc-cli to get the CLI side; a case synced by an older CLI picks up its tables, dataset and rule scenarios the next time its feature file changes. See
Setting up a BDD project and
Keeping test cases in sync with your repo.
