Loading...
Loading...
Found 40 Skills
PHPUnit testing best practices and conventions guide. This skill should be used when writing, reviewing, or refactoring PHPUnit tests to ensure consistent, maintainable, and effective test suites. Triggers on tasks involving test creation, test refactoring, test configuration, code coverage, data providers, mocking, or PHPUnit XML configuration.
Check and configure code coverage thresholds and reporting
Write tests for the added lines that a pharn-ci report (the pharn-dev/pharn-ci GitHub Action or the `pharn-ci check` CLI, 0.1.x with Report v1 or 0.2.x with Report v2) lists as uncovered, so a pull request's diff coverage meets its threshold. Use when pharn-ci fails with DIFF_COVERAGE_BELOW_THRESHOLD, or the person asks to cover the lines pharn-ci reports, raise diff coverage, get the pharn-ci coverage check passing, or exclude a file from, lower or switch off the pharn-ci coverage gate (it explains what that changes and asks first). Adds tests only - never lowers the threshold, excludes files, edits the pharn-ci config or workflow (including the test-integrity and accept-label inputs), adds coverage-ignore comments, skips or focuses tests, weakens test scripts, or applies the accept label. Not for adding pharn-ci to a repository (pharn-ci-install) or the PHARN CLI (pharn-cli).
Provides UT-based code coverage report generation for OpenHarmony C/C++, supporting both full and incremental coverage analysis, and requires a test device to be connected through hdc. Use when: (1) the user requests full code coverage for a subsystem, part, module, test suite, or test case; if a report path is provided, parse it as the --output path; (2) the user requests incremental code coverage for a part, module, test suite, or test case, requiring git diff files; if a report path is provided, parse it as the --output path. Note: incremental coverage does not support the subsystem level. Activate when an OpenHarmony device must be connected to execute tests.