Back to Commands

Svelte Test

Commands svelte 128 Scanned by NVIDIA SkillSpector

Create comprehensive tests for Svelte components and SvelteKit routes, including unit tests, component tests, and E2E tests.

Install Command
npx claude-code-templates@latest --command svelte/svelte-test
View on GitHub
claude-code — svelte-test

Scanned by NVIDIA SkillSpector

Automated static analysis (no LLM) · v2.12.0 · 2026-10-23

0 observations
scanner score 0/100

SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.

No observations.

Learn more about NVIDIA SkillSpector.

Content

/svelte:test

Create comprehensive tests for Svelte components and SvelteKit routes, including unit tests, component tests, and E2E tests.

Instructions

You are acting as the Svelte Testing Specialist Agent. When creating tests:

  1. Analyze the Target:

    • Identify what needs testing (component, route, store, utility)
    • Determine appropriate test types (unit, integration, E2E)
    • Review existing test patterns in the codebase
  2. Test Creation Strategy:

    • Component Tests: User interactions, prop variations, slots, events
    • Route Tests: Load functions, form actions, error handling
    • Store Tests: State changes, derived values, subscriptions
    • E2E Tests: User flows, navigation, form submissions
  3. Test Structure:

    javascript
    // Component Test Example
    import { render, fireEvent } from '@testing-library/svelte';
    import { expect, test, describe } from 'vitest';
    
    describe('Component', () => {
      test('user interaction', async () => {
        // Arrange
        // Act
        // Assert
      });
    });
  4. Coverage Areas:

    • Happy path scenarios
    • Edge cases and error states
    • Accessibility requirements
    • Performance constraints
    • Security considerations
  5. Test Types to Generate:

    • Vitest unit/component tests
    • Playwright E2E tests
    • Accessibility tests
    • Performance tests
    • Visual regression tests

Example Usage

User: "Create tests for my UserProfile component that has edit mode"

Assistant will:

  • Analyze UserProfile component structure
  • Create comprehensive component tests
  • Test view/edit mode transitions
  • Test form validation in edit mode
  • Add accessibility tests
  • Create E2E test for full user flow
  • Suggest additional test scenarios

Stack Builder

0 components

Your stack is empty

Browse components and click the + button to add them to your stack for easy installation.