oh-xts-build-run_skill

Overview

This skill combines OpenHarmony XTS compilation and test execution into a single, automated workflow. It builds XTS test projects to produce HAP files, then runs the tests and presents consolidated results. Optional parameters let you target a specific package or API class for the run stage. Use this skill to streamline end-to-end XTS test runs with one command.

How this skill works

The skill first invokes the build step to update test lists, run the hvigorw tool, and verify that both main and test HAP artifacts are produced. If the build fails, the process stops and returns the build error. On successful build, it automatically determines the package name (from pack.info or module.json5) and invokes the run step, optionally passing --package and --api arguments. The run step executes tests, parses test statistics, and returns a unified output showing compile and test results.

When to use it

• You need a single command to compile XTS tests and then execute them end-to-end.
• You want automatic package detection to avoid manually specifying the test package.
• You need parsed test results and consolidated logs for CI or local verification.
• You want to target a specific package or API class during test runs.
• You need a fail-fast workflow that stops if compilation fails.

Best practices

• Ensure pack.info or module.json5 is present and up to date for automatic package detection.
• Run in a clean workspace so hvigorw produces deterministic HAP outputs.
• Pass --package or --api only when you need to override automatic detection.
• Inspect build logs first if the workflow stops; most failures originate in the compilation step.
• Integrate this skill into CI pipelines to simplify XTS test phases.

Example use cases

• Local developer runs one command to build an XTS test suite and immediately see pass/fail counts.
• CI job compiles XTS artifacts and runs tests, failing the pipeline on compile errors.
• Targeted test run for a single API class using --api to reproduce a failing test quickly.
• Automated nightly runs that build multiple modules and collect unified test reports.