fixing-skipped-tests

Use this skill when unskipping a test that was previously skipped.

Repositorio: ChromeDevTools/devtools-frontend
Última actividad en el origen: 30 de julio de 2026 a las 06:18
Idioma detectado de SKILL.md: inglés
Estrellas: 4019
Forks: 711

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/ChromeDevTools/devtools-frontend --skill fixing-skipped-tests

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

Fixing Skipped Tests

This skill outlines the workflow for fixing skipped tests in the DevTools codebase, typically given a Chromium bug link (e.g., crbug.com/1234567).

Workflow

Extract the Bug ID

The input is typically a bug link like crbug.com/<bugid>. Extract the <bugid> from the link.

Create a Branch

Create a new branch named fixed-<bugid>.
Ensure you use the instructions from the devtools-version-control skill to create and switch branches appropriately.

Search for the Skipped Tests

Search the test/TestExpectations file for the <bugid> to find skipped tests.
Tests are no longer skipped using .skip in the code, but rather by having a [ Skip ] expectation in test/TestExpectations.

Iterative Fix Process

Step 1: Remove the [ Skip ] expectation for one of the tests associated with the bug in test/TestExpectations (or change it to [ Pass Failure ] if you are investigating flakiness).
Step 2: Re-run the specific test using its exact test ID (e.g., npm run test path/to/foo.test.ts:test_name) 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 -- --repeat=20 path/to/foo.test.ts:test_name) to run the test multiple times to reproduce the flakiness. This flag works for both E2E and unit tests.
Step 3: Analyze the test failure and make the necessary fixes to the code or the test itself.
Step 4: Re-run the test to ensure the fix is correct.
Step 5: Remove the [crbug.com/<bugid>] prefix from the test name string in the code if it is present.
Step 6: Remove any comments directly above the test in the code that explain the reason why the test was skipped (e.g., // TODO(crbug...): Flaky).
Step 7: Apply the fix to the remaining tests, un-skipping them one by one or in batches by modifying test/TestExpectations, and verifying until all are passing.

Verify Full Build

Before finishing, run the full verification process (TypeScript checks, linters, full test run) as required by the repository best practices.