R003: 禁止恒真断言

To detect tautological assertions in ArkTS or TypeScript unit tests, scan source files ending in .ets, .ts, or .js for patterns like expect(true).assertTrue(). The scan reports each violation with the file path, line number, and surrounding it() block name.

Tautological assertions are test checks like expect(true).assertEqual(true) that always pass regardless of actual system behavior. They harm test quality by providing no real verification, creating false confidence that code is validated when tests effectively validate nothing.

To find useless test cases that always pass in OpenHarmony test code, scan for mandated tautology patterns including expect(false).assertFalse(). The scan matches these patterns within it() testcase blocks and returns structured findings with offending snippets and precise fix suggestions.

Tautology detection works with .ets, .ts, and .js files in OpenHarmony projects. The scanning mechanism targets all source files within test contexts, specifically identifying tautological assertion violations across these three file extensions.

To fix expect(true).assertTrue() statements, replace the hardcoded boolean with an assertion on actual values returned by the code under test. The detection output provides a precise remediation suggestion for replacing the tautology with meaningful API output validation.

You can scan all source files to report tautological assertion violations with line numbers. The scan outputs structured findings including the exact file path, line number, testcase name, offending snippet, and a suggested replacement for each violation found.