Agent Skills › ChromeDevTools/devtools-frontend › fixing-skipped-tests

fixing-skipped-tests

GitHub

修复 DevTools 代码库中之前被跳过的测试。通过提取 Bug ID、移除跳过期望、迭代修复代码或测试并重新运行验证，最终确保所有关联测试通过。

.agents/skills/fixing-skipped-tests/SKILL.md ChromeDevTools/devtools-frontend

Trigger Scenarios

需要修复被标记为 Skip 的测试收到 Chromium Bug 链接要求取消测试跳过

Install

npx skills add ChromeDevTools/devtools-frontend --skill fixing-skipped-tests -g -y

More Options

Non-standard path

npx skills add https://github.com/ChromeDevTools/devtools-frontend/tree/main/.agents/skills/fixing-skipped-tests -g -y

Use without installing

npx skills use ChromeDevTools/devtools-frontend@fixing-skipped-tests

指定 Agent (Claude Code)

npx skills add ChromeDevTools/devtools-frontend --skill fixing-skipped-tests -a claude-code -g -y

安装 repo 全部 skill

npx skills add ChromeDevTools/devtools-frontend --all -g -y

预览 repo 内 skill

npx skills add ChromeDevTools/devtools-frontend --list

SKILL.md

Frontmatter

{
    "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 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.