Skip to content

TRCLI Release v1.16.0 - #476

Merged
damianoferrari merged 65 commits into
mainfrom
release/1.16.0
Oct 30, 2026
Merged

damianoferrari merged 65 commits into
mainfrom
release/1.16.0

Conversation

@acuanico-tr-galt

Copy link
Copy Markdown
Contributor

Added

  • Automatic creation of the automation_id field: When the field is missing in TestRail, trcli now offers to create it for easier startup. Note: Using -n no longer skips the automation_id check and Missing sections are also no longer gated by -y/-n.
  • Robot Framework parser improvements (parse_robot): Now supports Robot Framework 6.x and 7.x reports, mirrors the suite tree as nested TestRail sections, and extracts all keyword calls (including nested ones) as steps with their log output.
  • Robot Framework tag support: jira:, refs: and Jira-key-style tags are now added as case references, and priority:<level> tags set the case priority (customizable via new --priority-tag-mapping option).
  • Robot Framework step content now includes keyword arguments: Note: Re-uploading to existing cases may duplicate or update their steps. Keyword arguments and log output are uploaded by default; use the new --no-step-args and --no-step-logs options to exclude sensitive data.
  • Robot Framework sections are now nested using the suite name instead of a single dotted name: Note: Re-uploading to existing projects will create new sections.
  • --update-existing-cases and --update-strategy for parse_robot: Update references of existing TestRail cases from Robot Framework reports.
  • AI fields in cases command: cases get and cases list now show whether a case is AI generated and AI automated.
  • New reports command: List available report templates and generate reports in TestRail using list and generate subcommands.
  • New sharedsteps command: Manage shared steps in TestRail, supports listing, showing, creating, updating and deleting shared steps.

Fixed

  • Fixed an issue where the confirmation prompt for creating missing entities did not appear when neither -y nor -n was specified.
  • Fixed an issue where --verify failed with an error when a returned case field was missing, such as with the automation_id field.

…nds for retrieving and generating report templates via API
…n TestRail, allows creation, listing/showing, updating and deletion of shared steps
…gs from shared steps, also fixed updating with shared step name only
… requirements.txt to mirror dependency for test environment, also updated tox.ini with robot framework matrix factors consistent with the existing per-dependency version-matrix pattern
…s deep, multi-style arguments, all log levels, tags, diverse failures), this was executed through real RF 5.0.1 and RF 7.4.2 to generate genuinely schema-valid output.xml fixtures, also updated robot_parser unit test
…lity fixes, also catched robot.errors.DataError when handling malformed result data
…fected by an inherent RF <7.0 library limitation also fixed a pre-existing malformed timestamp blocking ExecutionResult parsing
Updated PR-validation check workflow
…eps extraction, also added RF60 and RF70 format test data with updated unit tests
…framework parser, updated reader with extract_steps and build_step
…ccording to input test result, also updated data classes, results uploader logic to properly handle clean up
…3 whitebox unit tests in tests/test_robot_nested_parser.py that had encoded the old (buggy) exclusion behavior
…ntion in cmd_labels.py, cmd_import_gherkin.py, multisuite_uploader.py
…d-incompatible step content format change (KeywordName(args) vs KeywordName) and the FAIL/SKIP actual fix, also added a one-time informational log warning users that re-uploading may duplicate/update existing TestRail steps due to the new content format, pointing to the CHANGELOG for details, _LOGGED_MESSAGE_LEVELS now includes FAIL/SKIP, with a corrected comment explaining that RF genuinely attaches diagnostic text at these levels
…handle_case_update_reporting; after upload, collects case_update_results from the uploader and reports via the shared helper, mirrors parse_junit pattern
…ow exposing --update-existing-cases/--update-strategy and invoking handle_case_update_reporting,ResultsUploader.update_existing_cases_with_junit_refs() is reachable for Robot Framework runs
TR-20992: Reports command (list and generate)
TR-20993: Shared Steps command (list, show, create, update, delete)
TR-21908: Added official robot framework dependency
TR-21909: Create Comprehensive Test Data for Robot Framework
TR-21910: Robot framework parser to use ExecutionResult API
TR-21911: Robot framework parser nested keyword extraction with tests.
TR-21912: Reference extraction for Robot Framework
TR-22030: Section Hierarchy Update for Robot Parser
TR-22028: Priority tag mapping for Robot Parser
TR-21906: Display AI automated and generated fields for cases list and get commands
TR-22340: Automation_ID automatic field creation
TR-22344: Unit tests for automation_id field auto creation
TR-22345: Added short README update for automatic creation of Automation ID
…response are now appended to responses before the verify check with updated test assertions, also the lookup is now skipped for sections whose parent exists locally but has no section_id which is marked as missing
@damianoferrari
damianoferrari merged commit ff097e4 into main Oct 30, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants