TRCLI-21: Interim support for BDD from JUnit test results via --special-parser bdd option under parse_junit #382
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…data and gherkin test script
… and functional tests
…l backoff for large projects
…led upload e.g. due to large file size
…erkin and cucumber json
…in, parse cucumber and gherkin with sample data and reports
…erkin commands also updated readme file with comprehensive guide
TRCLI-205 Updated payload format for adding labels to projects
TRCLI-202 Updated file attachment handling and display errors for failed upload due to large file size
TRCLI-203 Improved error handling and uploading for large dataset
TRCLI-207 Fix test run cases deletion issue in update_run_in_plan_entry
Merged bug fixes and improvements from release/1.12.5 into feature/TRCLI-21 branch: From release/1.12.5: - TRCLI-207: Fixed deletion issue when updating test runs - TRCLI-202: Updated file attachment handling and display errors for failed upload - TRCLI-203: Added parallel pagination feature with retry logic - TRCLI-205: Updated payload format for adding labels - Various test updates and improvements Kept feature/TRCLI-21 changes: - Version 1.13.0 (BDD/Gherkin support) - New BDD test methods and e2e tests - Gherkin parser functionality Resolved conflicts in: - CHANGELOG.MD: Combined both release notes - trcli/__init__.py: Kept version 1.13.0 - trcli/constants.py: Added attachment error messages - trcli/api/api_request_handler.py: Applied label payload fixes and include_all handling - trcli/cli.py: Added --parallel-pagination option - tests/test_api_request_handler.py: Kept both BDD and update_run tests - tests_e2e/test_end2end.py: Minor text adjustments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solution description
Allow support for JUnit-based test results to be posted to a correct BDD template test case.
Changes
Added a new option 'bdd' for --special-parser which allows users to trigger BDD mode (this also cross checks that a BDD test case is existing in TestRail before uploading)
Potential impacts
None
Steps to test
PR Tasks