docs: add JUnit XML Reports page

[PrathamSikka24]

What has changed?

Adds a new docs page — JUnit XML Reports — under Integration Testing in the sidebar (after Time Freezing).

The page covers:

• --format junit flag usage on keploy report
• JUnit XML output structure (test-sets → <testsuite>, failures → <failure>, obsolete → <skipped>)
• CI configuration examples for GitHub Actions, GitLab CI, Jenkins, and CircleCI

This documents the feature introduced in keploy/keploy#3955.

Type of change

• Bug fix
• New feature
• Breaking change
• Documentation update

How Has This Been Tested?

• Ran npm run build locally — no errors
• Verified page renders correctly at localhost:3000/docs/keploy-cloud/junit-xml-reports
• Confirmed sidebar entry appears after Time Freezing

Checklist

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.

[Copilot]

Pull request overview

Adds documentation for exporting Keploy test results as JUnit XML and wires the new page into the v4.0.0 docs sidebar under Integration Testing.

Changes:

• Adds a new docs page: JUnit XML Reports (usage, XML structure, CI examples).
• Registers the page in version-4.0.0-sidebars.json after Time Freezing.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.

File	Description
versioned_sidebars/version-4.0.0-sidebars.json	Adds the new keploy-cloud/junit-xml-reports entry to the Integration Testing sidebar section.
versioned_docs/version-4.0.0/keploy-cloud/junit-xml-reports.md	New page describing keploy report --format junit, output structure, and CI configuration snippets.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The intro claims CI systems parse the JUnit output “natively, no plugins or custom parsers needed”, but the GitHub Actions example below requires an external action to publish results. Consider rewording to something like “most CI systems can ingest JUnit XML” (and note that some, e.g. GitHub Actions, require a publishing step).

Suggested change

	Keploy supports exporting test results as standard JUnit XML. Use `--format junit` flag on the `keploy report` command — CI systems parse the output natively, no plugins or custom parsers needed.
	Supported CI systems: GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure DevOps.
	Keploy supports exporting test results as standard JUnit XML. Use the `--format junit` flag on the `keploy report` command — most CI systems can ingest JUnit XML, though some (like GitHub Actions) require a separate step to publish the results.
	Supported CI systems include: GitHub Actions, GitLab CI, Jenkins, CircleCI, Azure DevOps.

[PrathamSikka24]

Made the necessary changes and reworded this section in the docs.

[Copilot]

This page documents keploy report --format junit, but the v4.0.0 CLI reference (running-keploy/cli-commands.md) doesn’t list a --format flag for report. To avoid confusing readers, please either update the CLI reference in this version or add a note/link clarifying where this flag is documented and from which Keploy version it’s available.

[PrathamSikka24]

Added the --format flag to the report command in versioned_docs/version-4.0.0/running-keploy/cli-commands.md, including usage examples and a link back to this page.

[Copilot]

In GitHub Actions, if keploy test fails (which is when the JUnit report is most valuable), subsequent steps won’t run by default—so the report may never be generated/published. Adjust the example to ensure the report generation and publishing steps run even when tests fail (e.g., by using an always-run condition and/or capturing the test exit code).

[PrathamSikka24]

There were several examples of CI providers, so it makes more sense to keep one example because the configuration process is similar across all CI providers.

[slayerjain]

@PrathamSikka24 please handle the GitHub copilot comments. The related PR in keploy is now merged.