758: Added junit report to workflow

[Arshadul-Monir]

758

Description of changes

Added junit-report action to github workflow
https://github.com/mikepenz/action-junit-report

Checklist before review

• I have done a thorough self-review of the PR
• Copilot has reviewed my latest changes, and all comments have been fixed and/or closed.
• If I have made database changes, I have made sure I followed all the db repo rules listed in the wiki here. (check if no db changes)
• All tests have passed
• I have successfully deployed this PR to staging
• I have done manual QA in both dev (and staging if possible) and attached screenshots below.

Screenshots

Dev

Schecks showing which tests are wrong:

Staging

[github-actions]

Available PR Commands

• /ai - Triggers all AI review commands at once
• /review - AI review of the PR changes
• /describe - AI-powered description of the PR
• /improve - AI-powered suggestions
• /deploy - Deploy to staging

See: https://github.com/tahminator/codebloom/wiki/CI-Commands

[github-actions]

Title

758: Added junit report to workflow

---

PR Type

Enhancement, Tests

---

Description

• Add junitReport CI job for reports

• Use mikepenz/action-junit-report@v6

• Enable detailed summary in output

• Run step on success or failure

---

Diagram Walkthrough

flowchart LR
  backend["Backend Tests"] -- "produces JUnit results" --> junit["Publish JUnit Test Report"]
  junit -- "summary and annotations" --> gh["GitHub UI"]

Loading

File Walkthrough

	Relevant files
Configuration changes	ci-cd.yml Introduce CI job to publish JUnit reports                                .github/workflows/ci-cd.yml Add junitReport job publishing JUnit results Use mikepenz/action-junit-report@v6 Enable detailed_summary: true in action Step runs on success or failure +11/-0

---

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 Security concerns Third-party action pinning: the workflow uses 'mikepenz/action-junit-report@v6' pinned only to a major tag. Consider pinning to a specific commit SHA to reduce supply chain risk.

⚡ Recommended focus areas for review Ordering/Dependencies The new 'junitReport' job does not declare a dependency on the backend test job and uses only a step-level condition. To meet the acceptance criteria (run after the backend-test Bun script and surface failures), add a job-level 'needs: ' and 'if: always()' so it executes even if tests fail. junitReport: name: Publish Test Report runs-on: ubuntu-latest steps: - name: Publish JUnit Test Report uses: mikepenz/action-junit-report@v6 if: success() || failure() with: detailed_summary: true Missing report_paths The JUnit report action is invoked without 'report_paths', so it may not find any test result XML files. Point it to the JUnit XML(s) produced by the backend-test script (e.g., report_paths: '/junit//*.xml' or the actual backend output path). - name: Publish JUnit Test Report uses: mikepenz/action-junit-report@v6 if: success() || failure() with: detailed_summary: true No artifact handoff The JUnit report runs in a separate job and won’t have access to test result files from the backend test job unless they are uploaded and then downloaded as artifacts (or the report runs in the same job). Add upload in the test job and download here, then set 'report_paths' to the downloaded files. junitReport: name: Publish Test Report runs-on: ubuntu-latest steps: - name: Publish JUnit Test Report uses: mikepenz/action-junit-report@v6 if: success() || failure() with: detailed_summary: true

[Arshadul-Monir]

/improve

[github-actions]

PR Code Suggestions ✨

No code suggestions found for the PR.

[Arshadul-Monir]

/deploy