OpenParable
Skip to content
← Back to skills

Fixing Skipped Tests

Testing & Quality
fixing-skipped-tests

Fixing Skipped Tests is an Agent Skill for testing & quality published in the ChromeDevTools/devtools-frontend repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/ChromeDevTools/devtools-frontend/blob/HEAD/.agents/skills/fixing-skipped-tests/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/fixing-skipped-tests, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

  1. Extract the Bug ID

    • The input is typically a bug link like crbug.com/<bugid>. Extract the <bugid> from the link.
  2. 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.
  3. 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.
  4. 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.
  5. Verify Full Build

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