Results for “component-testing”

Guides writing behavior-focused React component and hook tests with React Testing Library, Vitest/Jest, MSW network mocking, and axe accessibility assertions, including when to use component vs end-to-end tests.

Provides best practices for writing JavaScript/TypeScript tests using Jest, including test structure, mocking strategies, async testing, snapshot testing, and React component testing.

Generates Jest unit and integration tests in JavaScript or TypeScript, covering mocking, snapshots, async testing, and React component testing.

Provides Vue.js testing best practices, patterns, and solutions for common pitfalls using Vitest, Vue Test Utils, and Playwright.

Write behavior-focused React component tests with React Testing Library, Vitest/Jest, MSW for network mocking, and accessibility assertions using axe, while deciding when to use component tests versus Playwright/Cypress end-to-end tests.

Write unit and integration tests for Angular v20+ applications using Vitest or Jasmine with TestBed and modern testing patterns. Use for testing components with signals, OnPush change detection, services with inject(), and HTTP interactions. Triggers on test creation, testing signal-based components, mocking dependencies, or setting up test infrastructure. Don't use for E2E testing with Cypress or Playwright, or for testing non-Angular JavaScript/TypeScript code.

Cypress E2E testing framework. Covers commands, assertions, and component testing. Use for end-to-end testing. USE WHEN: user mentions "cypress", "e2e test", "cy.get", "cy.visit", asks about "cypress intercept", "component testing", "cypress commands" DO NOT USE FOR: Unit tests - use `vitest` or `jest`; Multi-tab scenarios - Cypress doesn't support; Native mobile apps - use Appium; Performance testing - use dedicated tools

Write Jest or Vitest unit tests with React Testing Library and Playwright E2E tests for Next.js projects. Use when testing components with RTL, mocking APIs with MSW, or creating Playwright user flow tests.

Use when writing or modifying tests for Ink (terminal UI) components.

Builds React 18+ components, implements custom hooks, debugs rendering issues, migrates class components to functional, and manages state with Context, Redux, or Zustand. Covers React 19 Server Components, Suspense boundaries, useActionState forms, and performance optimization.

Routes to 82 Lightning Web Components skill packages covering reactivity, wire adapters, component communication, accessibility, performance, security, and Jest testing. Finds and opens the exact skill package for LWC-related requests.

Converts Stitch designs into modular Vite and React components, or syncs existing components to match updated designs.

Converts Stitch designs into modular Vite and React components using system-level networking and AST-based validation.

Use when writing or modifying tests for React hooks.

Writes Jest unit tests for Lightning Web Components using @salesforce/sfdx-lwc-jest, covering wire adapter mocks, imperative Apex mocking, and async rerender handling.

Audits Vue 3 components for design-system consistency, legacy patterns, and missing states, producing a component log.

Converts Stitch designs into modular Vite and React components, or syncs/updates existing React components to align with the latest Stitch designs, using system-level networking and AST-based validation.

Generates Angular 17+ standalone components, configures advanced routing with lazy loading and guards, implements NgRx state management, applies RxJS patterns, and optimizes bundle performance.

Converts Stitch designs into modular Vite and React components, using MCP networking and AST-based validation to ensure code quality.

Vitest testing framework. Covers unit tests, mocking, and coverage. Use for testing Vite-based and Node.js projects. USE WHEN: user mentions "vitest", "vite test", "unit test", asks about "vi.fn", "vi.mock", "test coverage", "mock functions", "test vite project" DO NOT USE FOR: E2E tests - use `playwright` instead; React component testing - combine with `testing-library`; Jest projects - use `jest` instead

Provides expert guidance for testing Spring Boot 4 applications with modern patterns, test slices, and best practices.

Create or review Blazor components (.razor files) with correct architecture, covering parameters, EventCallback, RenderFragment, lifecycle, async patterns, disposal, and CSS isolation.

Creates complete AEM components with dialog, HTL template, Sling Model, unit tests, and clientlibs. Supports extending Core Components and project components, and can translate Figma designs into pixel-perfect HTL, CSS, and JS.

`analysis-agent`/`task-agent`/`review-agent`: use for database, broker, cache, HTTP, framework, process, or transaction seam proof; skip local, portfolio, and release-verdict work.

Cpp Testing

Generate tests, design test strategies, and ensure code quality through testing. Use when writing tests, improving test coverage, designing test infrastructure, or evaluating test quality.

CI security scanning: secrets, deps, SAST, triage, expiring exceptions

`analysis-agent`/`task-agent`/`review-agent`: use for component, route, browser, accessibility, and API-backed UI-state tests; skip backend, portfolio, and release-verdict work.

Generates Angular code and provides architectural guidance for projects, components, services, reactivity, forms, dependency injection, routing, accessibility, animations, styling, testing, and CLI tooling.

Builds an evidence-backed ECC install plan for a repository by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes.