Menu
Use this skill when unskipping a test that was previously skipped.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when migrating Chromium layout tests to DevTools unit tests
Use when starting a new task, creating a branch, switching branches, managing branches, creating and uploading CLs, handling stacked changes, or checking release and roll status in the DevTools Gerrit-based workflow. ALWAYS use this instead of running standard git checkout/switch commands for branch creation.
Reproduce and investigate flakiness in a test.
Refactor user-facing UIStrings and localization comments in a DevTools module folder according to UX writing guidelines (child task of b/40799900). Use when simplifying wording, checking sentence case, or improving L10n comments in UIStrings for a specific folder or issue. Don’t use for general code changes or non-UIStrings files.
Migrates legacy imperative DOM construction to local declarative Lit-html templates rendered inside existing containers.
Consolidates manual DOM creation, updates, and constructors into private helper methods and structured state interfaces.
| name | fixing-skipped-tests |
| description | Use this skill when unskipping a test that was previously skipped. |
This skill outlines the workflow for fixing skipped tests in the DevTools codebase, typically given a Chromium bug link (e.g., crbug.com/1234567).
Extract the Bug ID
crbug.com/<bugid>. Extract the <bugid> from the link.Create a Branch
fixed-<bugid>.devtools-version-control skill to create and switch branches appropriately.Search for the Skipped Tests
<bugid> to find skipped tests.it.skip('[crbug.com/<bugid>] ...', ...) or skipped describes that mention the bug ID.Iterative Fix Process
it.skip or describe.skip to it.only or describe.only for one of the tests associated with the bug, so that only that specific test runs.npm run test -- <path_to_test_file>) using the guidelines from the devtools-verification skill. If you are dealing with flaky tests, you can use the --repeat=x flag (e.g. npm run test -- <path_to_test_file> --repeat=20) to run the test multiple times to reproduce the flakiness..only.[crbug.com/<bugid>] prefix from the test name string if it is present.// TODO(crbug...): Flaky).Verify Full Build