xts-generator

You generate OpenHarmony XTS tests by providing js-apis-* Markdown API documentation to derive standardized Hypium .ets test files. This extracts module signatures, parameters, return types, and error codes to automate normal, exception, and optional-parameter coverage.

Writing Hypium tests with strict ETS type safety requires explicit types and forbids any or unknown usage. This standardizes test generation to enforce single error-code assertions and English-only logs for robust OpenHarmony validation.

XTS test generation supports enum value and file path or URI scenario coverage. It systematically produces numbered test cases for these specific scenarios alongside normal, null, undefined, and optional-parameter combination tests from API definitions.

Yes, you can use js-apis Markdown files to create exception and null case tests. The generation process extracts error codes and parameter constraints directly from the documentation to build targeted exception and null or undefined validation cases.

Ensuring correct subsystem and module naming in generated ETS tests requires deriving names directly from the parsed js-apis Markdown documentation. This mechanism automatically maps API module signatures to their appropriate subsystem and module naming conventions.

Limitations when generating Hypium tests include strict dependencies on the presence of js-apis Markdown documentation for parsing. Additionally, the output enforces strict ETS type safety by forbidding any or unknown types and requiring single error-code assertions.