fixing-skipped-tests

星标3,971

分支690

更新时间2026年6月30日 14:38

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

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

ChromeDevTools

ChromeDevTools/devtools-frontend

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

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 codebase for the <bugid> to find skipped tests.
- You should look for occurrences like it.skip('[crbug.com/<bugid>] ...', ...) or skipped describes that mention the bug ID.
Iterative Fix Process
- Step 1: Change 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.
- Step 2: Re-run the tests (e.g., 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.
- 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. Remove .only.
- Step 5: Remove the [crbug.com/<bugid>] prefix from the test name string if it is present.
- Step 6: Remove any comments directly above the test 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, 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.

同仓库更多 Skills

同仓库

devtools-migrate-chromium-test

ChromeDevTools/devtools-frontend

Use when migrating Chromium layout tests to DevTools unit tests

2026-07-094.0k

devtools-version-control

ChromeDevTools/devtools-frontend

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.

2026-07-094.0k

repro-flaky-test

ChromeDevTools/devtools-frontend

Reproduce and investigate flakiness in a test.

2026-07-074.0k

devtools-ux-writing-refactor

ChromeDevTools/devtools-frontend

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-07-074.0k

ui-eng-vision-local-lit-renderer

ChromeDevTools/devtools-frontend

Migrates legacy imperative DOM construction to local declarative Lit-html templates rendered inside existing containers.

2026-07-024.0k

ui-eng-vision-logic-consolidator

ChromeDevTools/devtools-frontend

Consolidates manual DOM creation, updates, and constructors into private helper methods and structured state interfaces.

2026-07-024.0k

name	fixing-skipped-tests
description	Use this skill when unskipping a test that was previously skipped.

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 codebase for the <bugid> to find skipped tests.
- You should look for occurrences like it.skip('[crbug.com/<bugid>] ...', ...) or skipped describes that mention the bug ID.
Iterative Fix Process
- Step 1: Change 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.
- Step 2: Re-run the tests (e.g., 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.
- 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. Remove .only.
- Step 5: Remove the [crbug.com/<bugid>] prefix from the test name string if it is present.
- Step 6: Remove any comments directly above the test 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, 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.