fixing-skipped-tests

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

Repository: ChromeDevTools/devtools-frontend
Letzte Quellaktivität: 30. Juli 2026 um 06:18
Erkannte Sprache von SKILL.md: Englisch
Sterne: 4.019
Forks: 711

Installationsoptionen

Standardmäßig ist der Prompt ausgewählt, der zuerst die Quelle prüft. Sie können zu einem direkten Befehl wechseln oder eine lokale Kopie herunterladen.

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.

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

Der Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.

Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.

Quelldateien prüfen

Lesen Sie SKILL.md und alle von SkillsMP angezeigten Begleitdateien, bevor Sie sich für eine Installation entscheiden.

SKILL.md

Quellanweisungen · Schreibgeschützte Vorschau

Zurück zur Suche Zurück zur Installation

gerrit-cli

Interacts with the public Gerrit Code Review platform using depot_tools' gerrit_client.py. Use this skill when asked to query public CLs, retrieve published review comments, inspect formatted patches or complete file revisions, add patchset comments, vote on review labels, submit changes, or abandon/restore public CLs. Do not use this skill for Google-internal attention set updates or internal AI-assisted code reviews (CRUAS), which are unsupported by the public API.

2026-08-27

devtools-ux-writing-refactor

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.

2026-08-07

devtools-ci

Triage and analyze Chromium/DevTools LUCI build results and trybot failures, including high-level builder status, compile errors, and detailed test failures. Use this to inspect trybot buildbucket (bb) results for a patchset overview or to query ResultDB directly for comprehensive, actionable information about specific test regressions and infrastructure issues.

2026-07-28

Alle aus diesem Repository ansehen

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.