openharmony-ut

To run OpenHarmony unit tests on a device using hdc, you need to provide the project root, build output path, build command, and Windows host IP. The workflow validates hdc connectivity, deploys the artifacts, and executes the specified test target.

OpenHarmony fuzz testing on real devices involves generating, compiling, deploying, and executing tests through an automated workflow. It validates device connectivity via hdc port checks and target listing before running the fuzz test targets to ensure reliable execution.

Yes, you can execute existing OpenHarmony test artifacts without recompiling by using the "only run" flow. This mode reuses existing build outputs if present, allowing you to quickly deploy and run the specified UT or FuzzTest targets on a connected device.

Yes, validating hdc connectivity is required before deploying OpenHarmony tests. The workflow performs connectivity validations including pinging the Windows host IP, checking the hdc port, listing targets, and verifying shell access to ensure reliable device deployment.

To regenerate and validate OpenHarmony tests after code changes, use the "write then run" flow. This automated loop handles test generation, compilation, deployment, and on-device execution, iterating through fixes until the modified UT or FuzzTest target passes.