oh-capi-xts-gen

Generating OpenHarmony CAPI XTS tests from C header files involves parsing .h API declarations to extract function signatures, then producing C++ N-API wrapper code and matching ETS/ArkTS test cases following hypium naming conventions.

N-API mode-2 testing in OpenHarmony wraps C APIs into C++ N-API modules for ETS/ArkTS invocation. It is needed when validating CAPI subsystems via XTS test suites, requiring strict triple verification across C++ registration, index.d.ts declarations, and ETS testNapi calls.

Yes, you can use coverage reports to generate incremental missing CAPI test cases. By providing coverage reports or missing test items, the system generates supplementary tests for missing APIs, parameter combinations, or test scenarios without performing redundant full-suite analysis.

Yes, OpenHarmony CAPI XTS generation supports compilation verification for N-API wrappers. After enforcing N-API triple consistency checks, it can execute optional compilation verification workflows on Linux and Windows to validate the generated C++ and ETS/ArkTS test code.

A key limitation of automated CAPI XTS test generation is its strict enforcement of mode-2 (N-API) only, meaning it does not support other testing modes. Additionally, it requires precise C header parsing and mandatory triple verification to prevent registration or declaration inconsistencies.