Unit Test Reports

Ambari Product Reports

After Maven tests, inspect the module that was actually executed:

• Java unit tests: ambari-server/target/surefire-reports/
• Functional-module Surefire tests: ambari-funtest/target/surefire-reports/
• Functional-module Failsafe tests: ambari-funtest/target/failsafe-reports/
• Agent Python runner log: ambari-agent/target/tests.log, together with captured test output and exit status
• Server Python runner: captured stdout/stderr, including discovered test totals, failures, and exit status

The default Python runners use text test results. They do not automatically produce python-test-results or python-coverage directories; collect coverage separately with the tooling selected by the validation job.

Reports are evidence for the selected Maven reactor and profile. A skipped suite has no passing report, and a failure ignored by Maven remains a failure in the report.

The paths and output behavior are defined by the pinned Agent runner, Server runner, and functional-test module.

Build And Packaging Reports

Review module target directories for RPMs, wheel metadata, dependency audits, and SBOM output. The packaged CPython 3.9 ABI and platform profile must match the artifact under review.

Website Reports

Website checks are separate from Ambari product tests:

• yarn test:i18n reports Markdown structure, links, images, and locale coverage.
• yarn test:e2e reports browser behavior for the website/UI build.

These checks do not certify Server, Agent, Stack, KDC, database, or real-cluster behavior.

Interpreting Results

Record the exact command, module/profile, runtime versions, skipped suites, and report paths. For a release or runtime change, combine focused reports with representative Server/Agent and Stack validation; do not infer end-to-end acceptance from a single dashboard, website check, or generated XML file.