Elian Doran f804609745 ci: run ckeditor5-utils as a browser-mode suite with chromedriver ... The ckeditor5-utils package runs its tests in WebdriverIO + headless Chrome, but the CI workflow never registered it as a browser-mode suite. It fell into the catch-all "Run the rest of the tests" step, which has no CHROMEDRIVER_PATH exported, so WebdriverIO tried to auto-download chromedriver into /tmp and failed on a partial cache. Give it a dedicated step that exports CHROMEDRIVER_PATH (like the mermaid/math/aggregate suites), run it with --coverage, upload the coverage and test results to Codecov under a ckeditor5-utils flag, and exclude it from the catch-all step. Enabling --coverage surfaced a real gap (98.19% vs the package's 100% threshold): the function-form customClass path in _customClass() was untested. Add a test covering it so the suite lands at 100%. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>		2026-07-16 22:44:47 +03:00
..
actions	chore(deps): update actions/checkout action to v7	2026-06-21 00:28:05 +00:00
ISSUE_TEMPLATE	chore(monorepo): put back CI and environment setup	2025-04-18 16:10:03 +03:00
workflows	ci: run ckeditor5-utils as a browser-mode suite with chromedriver	2026-07-16 22:44:47 +03:00
FUNDING.yml	feat(funding): add Buy Me a Coffee	2025-07-12 23:28:07 +03:00