R002: 错误码断言必须是number类型

You should assert error.code using number literals instead of string numeric literals to prevent type-mismatch test failures. Replacing string assertions like "401" with numeric values ensures correct type checking and accurate test validation in OpenHarmony test code.

Scan OpenHarmony ets/ts/js test files to detect type-mismatch assertions where error.code is compared using string numeric literals. The detection matches assertEqual, assertTrue, and if-condition patterns while filtering out comments and non-assert usages, listing flagged numeric strings.

Yes, error code type checking supports basic variable tracking by identifying string-typed variables, constants, and parameters later compared against error.code. It handles catch-block alias cases, ensuring string variables used in assertions are traced and flagged for type mismatches.

No, the error code assertion check filters out comments, console logging, and non-assert usages. It only flags cases where the asserted string is a pure numeric literal like "401" or "14000011", ensuring non-numeric string values are not reported as type mismatches.

The best way to fix type-mismatch assertions for OpenHarmony error codes is to scan test files and convert numeric string literals to number literals. Automatically list every place where error.code is compared using strings, then replace them with numeric values for proper type checking.