oh-xts-build-run

Name: oh-xts-build-run
Availability: InStock
Author: openharmonyinsight

Build and run OpenHarmony XTS test projects, generating HAP artifacts and summarizing execution statistics.

31|6|Updated Jan 29, 2026

Search Tags:#build #test execution #openharmony #hap #xts #hvigorw #ci diagnostics

Ready to run

npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill oh-xts-build-run

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oh-xts-build-run
Source: https://github.com/openharmonyinsight/openharmony-skills/tree/main/skills/oh-xts-build-run
Command: npx skills add https://github.com/openharmonyinsight/openharmony-skills --skill oh-xts-build-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual two-step process of compiling an OpenHarmony XTS test project and then running it to collect and inspect results, reducing time-to-feedback when verifying changes.

Core Features & Use Cases

Unified build + run workflow: Runs /oh-xts-build to produce the required HAP artifacts, then automatically proceeds to /oh-xts-run to execute the tests.
Result validation and reporting: Stops early when compilation fails; otherwise parses and summarizes XTS execution statistics into a single combined output.
Flexible runtime targeting: Supports passing --package to select a package and --api to target a test class during the run stage.

Use case example: After updating an XTS test suite, compile the test artifacts and immediately run the relevant tests while capturing both compilation output and execution statistics in one run.

Quick Start

Run the XTS build-and-run workflow and optionally focus on a specific package and test class by issuing: /oh-xts-build-run --package=<package-name> --api=<api-name>.

Frequently Asked Questions about oh-xts-build-run

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I build and run OpenHarmony XTS tests in one step?▼

To build and run OpenHarmony XTS tests in one step, use a unified workflow that compiles HAP artifacts via hvigorw and immediately executes the suite, removing the manual two-step process and delivering combined compile-to-execution feedback in a single run.

Can I target a specific package or API when running XTS tests?▼

Yes, you can target specific packages or APIs during XTS test execution by passing the --package and --api parameters, allowing you to focus the run on a selected package name or a specific test class.

What happens if the OpenHarmony XTS compilation fails?▼

If the OpenHarmony XTS compilation fails, the workflow stops early and does not proceed to the test execution stage, preventing wasted runtime by validating build outputs before attempting to parse execution statistics.

How do I get XTS execution statistics after compiling HAP artifacts?▼

To get XTS execution statistics after compiling HAP artifacts, run an automated workflow that validates the build output and then executes the tests, parsing runtime statistics into a single combined summary report for immediate feedback.

Do I need separate tools for OpenHarmony XTS build and test execution?▼

You do not need separate tools for OpenHarmony XTS build and test execution if you use a unified automation workflow that sequences the compilation and execution stages together, capturing both build outputs and execution statistics in one run.