TRCLI-213 Refactor core api handler class into separate handlers to improve code quality

.github/workflows/pr-validation.yml

@@ -23,30 +23,31 @@ jobs:
           PR_BODY="${{ github.event.pull_request.body }}"
 
           # Check if PR title or body contains issue reference
-          # Accepts: TRCLI-### (JIRA), GIT-### (GitHub), #123 (GitHub), issues/123
-          if echo "$PR_TITLE $PR_BODY" | grep -qE "TRCLI-[0-9]+|GIT-[0-9]+|#[0-9]+|issues/[0-9]+"; then
-            echo "issue_found=true" >> $GITHUB_OUTPUT
+          if echo "$PR_TITLE $PR_BODY" | grep -qE "(TRCLI-[0-9]+|GIT-[0-9]+|#[0-9]+|issues/[0-9]+)"; then
+            echo "issue_found=true" >> "$GITHUB_OUTPUT"
 
-            # Extract the issue key/number
             if echo "$PR_TITLE $PR_BODY" | grep -qE "TRCLI-[0-9]+"; then
               ISSUE_KEY=$(echo "$PR_TITLE $PR_BODY" | grep -oE "TRCLI-[0-9]+" | head -1)
-              echo "issue_key=$ISSUE_KEY" >> $GITHUB_OUTPUT
-              echo "issue_type=JIRA" >> $GITHUB_OUTPUT
+              echo "issue_key=$ISSUE_KEY" >> "$GITHUB_OUTPUT"
+              echo "issue_type=JIRA" >> "$GITHUB_OUTPUT"
+
             elif echo "$PR_TITLE $PR_BODY" | grep -qE "GIT-[0-9]+"; then
               ISSUE_KEY=$(echo "$PR_TITLE $PR_BODY" | grep -oE "GIT-[0-9]+" | head -1)
-              echo "issue_key=$ISSUE_KEY" >> $GITHUB_OUTPUT
-              echo "issue_type=GitHub" >> $GITHUB_OUTPUT
+              echo "issue_key=$ISSUE_KEY" >> "$GITHUB_OUTPUT"
+              echo "issue_type=GitHub" >> "$GITHUB_OUTPUT"
+
             elif echo "$PR_TITLE $PR_BODY" | grep -qE "#[0-9]+"; then
               ISSUE_KEY=$(echo "$PR_TITLE $PR_BODY" | grep -oE "#[0-9]+" | head -1)
-              echo "issue_key=$ISSUE_KEY" >> $GITHUB_OUTPUT
-              echo "issue_type=GitHub" >> $GITHUB_OUTPUT
+              echo "issue_key=$ISSUE_KEY" >> "$GITHUB_OUTPUT"
+              echo "issue_type=GitHub" >> "$GITHUB_OUTPUT"
+
             elif echo "$PR_BODY" | grep -qE "issues/[0-9]+"; then
               ISSUE_KEY=$(echo "$PR_BODY" | grep -oE "issues/[0-9]+" | head -1)
-              echo "issue_key=$ISSUE_KEY" >> $GITHUB_OUTPUT
-              echo "issue_type=GitHub" >> $GITHUB_OUTPUT
+              echo "issue_key=$ISSUE_KEY" >> "$GITHUB_OUTPUT"
+              echo "issue_type=GitHub" >> "$GITHUB_OUTPUT"
             fi
           else
-            echo "issue_found=false" >> $GITHUB_OUTPUT
+            echo "issue_found=false" >> "$GITHUB_OUTPUT"
           fi
 
       - name: Comment on PR if issue reference missing
@@ -61,42 +62,38 @@ jobs:
               repo: context.repo.repo,
               body: `## ⚠️ Missing Issue Reference
 
-              This PR does not reference an issue. Please include a reference in either:
+              This PR does not reference an issue. Please include one.
 
-              **JIRA tickets:**
-              - PR title: "feat(api): TRCLI-123 Add new endpoint"
-              - PR description: "Resolves TRCLI-123"
+              **JIRA example:**
+              - TRCLI-123
 
-              **GitHub issues:**
-              - PR title: "feat(api): GIT-123 Add new endpoint"
-              - PR description: "Resolves GIT-123" or "Fixes #123"
-              - Or link to the GitHub issue
-
-              This helps with tracking and project management. Thank you!`
+              **GitHub examples:**
+              - GIT-123
+              - Fixes #123
+              - issues/123`
             })
 
       - name: Check PR Description Completeness
         id: check_description
         run: |
           PR_BODY="${{ github.event.pull_request.body }}"
 
-          # Check for required sections
           if echo "$PR_BODY" | grep -q "Issue being resolved"; then
-            echo "has_issue=true" >> $GITHUB_OUTPUT
+            echo "has_issue=true" >> "$GITHUB_OUTPUT"
           else
-            echo "has_issue=false" >> $GITHUB_OUTPUT
+            echo "has_issue=false" >> "$GITHUB_OUTPUT"
           fi
 
           if echo "$PR_BODY" | grep -q "Solution description"; then
-            echo "has_solution=true" >> $GITHUB_OUTPUT
+            echo "has_solution=true" >> "$GITHUB_OUTPUT"
           else
-            echo "has_solution=false" >> $GITHUB_OUTPUT
+            echo "has_solution=false" >> "$GITHUB_OUTPUT"
           fi
 
           if echo "$PR_BODY" | grep -q "Steps to test"; then
-            echo "has_test_steps=true" >> $GITHUB_OUTPUT
+            echo "has_test_steps=true" >> "$GITHUB_OUTPUT"
           else
-            echo "has_test_steps=false" >> $GITHUB_OUTPUT
+            echo "has_test_steps=false" >> "$GITHUB_OUTPUT"
           fi
 
       - name: Generate PR Validation Summary
@@ -107,6 +104,7 @@ jobs:
             const issueFound = '${{ steps.check_issue.outputs.issue_found }}' === 'true';
             const issueKey = '${{ steps.check_issue.outputs.issue_key }}';
             const issueType = '${{ steps.check_issue.outputs.issue_type }}';
+
             const hasIssue = '${{ steps.check_description.outputs.has_issue }}' === 'true';
             const hasSolution = '${{ steps.check_description.outputs.has_solution }}' === 'true';
             const hasTestSteps = '${{ steps.check_description.outputs.has_test_steps }}' === 'true';
@@ -124,9 +122,9 @@ jobs:
             | Solution Description | ${hasSolution ? '✅ Present' : '⚠️ Missing'} |
             | Test Steps | ${hasTestSteps ? '✅ Present' : '⚠️ Missing'} |
 
-            ${issueFound && hasSolution && hasTestSteps ? '✅ All checks passed!' : '⚠️ Some optional sections are missing. Consider adding them for better review context.'}
+            ${issueFound && hasSolution && hasTestSteps
+              ? '✅ All checks passed!'
+              : '⚠️ Some optional sections are missing.'}
             `;
 
-            await core.summary
-              .addRaw(summary)
-              .write();
+            await core.summary.addRaw(summary).write();

CHANGELOG.MD

@@ -13,6 +13,19 @@ _released 12-01-2025
 ### Fixed
  - Added new BDD/Gherkin parser command parse_bdd for behavioral driven development-related testing
 
+### Added
+ - **BDD Support for parse_junit**: Added `--special-parser bdd` option to group multiple JUnit scenarios into a single TestRail BDD test case; supports case ID extraction, BDD case validation and result aggregation
+
+## [1.12.5]
+
+_released 12-09-2025
+
+### Fixed
+ - Added a new option --parallel-pagination for handling large test result uploads with optimized processing and improved error handling.
+ - Fixed an issue where adding labels to project fails using label add command
+ - Fixed an issue where failed attachment upload errors (e.g. due to file size being too large) is not displayed in standard output.
+ - Fixed an issue where test cases are deleted in existing test runs with configs in a test plan
+
 ## [1.12.4]
 
 _released 11-03-2025