check-test-code-quality

To check OpenHarmony XTS test code quality, scan your directory to detect assertion correctness, naming rules, and configuration violations across 23 Critical and Warning rules, generating structured issue records and an Excel report for triage.

Static analysis for XTS test suites applies 23 Critical and Warning rules covering assertion correctness, coding standard violations, naming constraints, configuration correctness, and common coding pitfalls to catch issues before build time.

Yes, you can automatically fix coding standard violations in XTS test cases using the optional --fix flag. This accelerates remediation for supported rules, including testcase formatting, naming corrections, and certain duplicate case removals.

Yes, XTS test code analysis supports filtering by specific rule levels. You can use the --level and --rules flags to honor rule selection, scoping the deterministic scanning to only Critical or Warning checks as needed.

You generate an Excel BOM-encoded report for XTS static analysis triage by running a scan on your project directory. The report includes detailed rule IDs, issue locations, and subsystem mapping for structured issue records.

The best way to detect duplicate test cases is to run project-level duplicate detection within independently identified XTS projects. This ensures results stay scoped and meaningful, preventing false positives across unrelated subsystems.