Results for “fix”

Guides writing a failing test before production code, iterating through red-green-refactor cycles, and fixing bugs test-first.

Automates end-to-end QA: starts the app, exercises screens and API endpoints, verifies functionality and design quality, runs domain analysis, and fixes issues found.

Implements features, fixes bugs, and refactors code by orchestrating domain-specific skills, following existing patterns, and verifying tests and lint pass.

Sets up Microsoft Testing Platform hot reload to iterate fixes on failing tests without rebuilding, covering package installation, environment configuration, and the iterative workflow.

Walks a running app across routes, states, and interactions to find real bugs, then root-causes, fixes, adds regression tests, and verifies each fix before committing.

Creates custom ESLint rules using the ESLint RuleTester API and AST Explorer patterns, generating rule implementations with auto-fix suggestions based on estree node types and scope analysis.

Interpret n8n validation errors and warnings, guide iterative fixes, and explain validation profiles, error types, and auto-sanitization.

Write, fix, and run C++ tests using GoogleTest/GoogleMock with CMake/CTest, including TDD workflows, coverage, and sanitizers.

Guides implementing features and bug fixes test-first, enforcing red-green-refactor with mandatory failure verification.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, to prevent false success claims.

Runs a disciplined debugging loop for hard bugs and performance regressions, covering reproduction, hypothesis testing, instrumentation, fixing, and regression testing.

Enforces a test-first workflow for features and bug fixes, guiding the red-green-refactor cycle with verification checklists.

Write tests before implementation code for new features, bug fixes, and refactoring, following the red-green-refactor cycle.

Fix build errors and breaking changes when upgrading MSTest from v3 to v4, or plan a complete migration.

Migrate .NET test projects from xUnit.net (v2 or v3) to MSTest v4, converting attributes, assertions, fixtures, and project configuration.

Guides implementing features and bug fixes test-first, enforcing the red-green-refactor cycle with mandatory failure verification.

Enforces running verification commands and confirming output before claiming work is complete, fixed, or passing, ensuring evidence precedes any success claims.

Verifies data structures, files, YAML blocks, or agent output against their defined schema, producing a pass/fail report with actionable fix instructions.

Generate, review, fix, and migrate Playwright end-to-end tests with templates, CI integration, and optional TestRail/BrowserStack sync.

Automates the cycle of fixing CI failures, addressing PR review feedback, and pushing changes until all checks pass.

Scaffolds eval.yaml test files for agent skills in the dotnet/skills repository, including scenario writing, assertion definition, and rubric creation.

Provides a workflow for writing, updating, and fixing C++ tests with GoogleTest/GoogleMock, configuring CMake/CTest, diagnosing failures, and adding coverage or sanitizers.

Runs a disciplined diagnosis loop for hard bugs and performance regressions, from reproduction through hypothesis testing, instrumentation, fixing, and regression testing.

Generates, reviews, fixes, and migrates Playwright end-to-end tests, with templates, agents, and integrations for TestRail and BrowserStack.

Drive development with tests by writing a failing test before implementing code, and reproduce bugs with tests before fixing them.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests for new features, bug fixes, or refactoring.

Runs a hypothesis-driven debugging workflow that reproduces failures, forms discriminating tests, proves root cause via toggle, and delivers a fix, regression test, and postmortem.

Runs a persistent verification-and-fix loop, executing existing test suites and browser/desktop checks until the requested surface is verified or a real blocker remains.

Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests for new features, bug fixes, and refactoring.

Refactors test files to improve behavioral coverage, clarity, structure, assertions, fixture setup, and mocking strategy, removing implementation-detail or low-value tests.