Feature
tc-cli: Zero-Setup CI Reporting with `--auto-create`
Upload test results to TestCollab from CI with no manual setup. The new `--auto-create` flag on `tc report` creates the tag, suites, test cases, folder, and test plan automatically from your result file.
Getting test results into TestCollab used to require pre-creating a test plan and tagging test cases. The new
- Smart matching — Tests with TC IDs (e.g.
- Mixed mode — Some tests can have IDs while others rely on title matching. Both work in the same result file.
- Suite name humanization — Raw test runner names like
- Reuses on subsequent runs — The tag, suites, folder, and test cases are reused on every run, so only a new test plan is created each time.
Works with both JUnit XML and Mochawesome JSON. See the auto-create docs for permission requirements and CI examples.
--auto-create flag on tc report removes all that setup.tc report --project 123 --format junit --result-file results.xml --auto-createCI Imported), test suites (humanized from classname/describe blocks), test cases, the CI test plan folder, and a fresh test plan named CI Run: DD-MM-YYYY HH:MM.- Smart matching — Tests with TC IDs (e.g.
[TC-42]) match by ID. Tests without IDs match by normalized title within the same suite. No match? A new test case is created.- Mixed mode — Some tests can have IDs while others rely on title matching. Both work in the same result file.
- Suite name humanization — Raw test runner names like
com.app.LoginTests, tests/auth/login.spec.ts, or UserProfileTests are automatically cleaned up into readable suite titles.- Reuses on subsequent runs — The tag, suites, folder, and test cases are reused on every run, so only a new test plan is created each time.
Works with both JUnit XML and Mochawesome JSON. See the auto-create docs for permission requirements and CI examples.
