sparq-testing

Establish testing standards and edge-case coverage for the Sparq Connection codebase.

Updated Feb 24, 2025
One-click install
npx skills add https://github.com/KrisWemet/sparq-connection-lab --skill sparq-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sparq-testing
Source: https://github.com/KrisWemet/sparq-connection-lab/tree/main/.claude/skills/sparq-testing
Command: npx skills add https://github.com/KrisWemet/sparq-connection-lab --skill sparq-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This section describes the need for rigorous testing standards, patterns, and edge-case coverage to keep Sparq's codebase stable as features grow.

Core Features & Use Cases

  • Establishes conventions for E2E Playwright tests, unit tests with Vitest, and integration tests to catch regressions early.
  • Provides mock data patterns, test infrastructure guidance, and clear expectations for psychology-based personalization, partner sync, and streak/daily-reset logic.
  • Supplies example workflows and decision criteria to determine when tests should be added alongside feature code.

Quick Start

Draft and execute a comprehensive test plan for new features, starting with an end-to-end Playwright workflow to validate critical user flows.

Frequently Asked Questions about sparq-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write E2E Playwright tests for new features?

Vitest unit tests catch regressions early by establishing conventions for isolated component testing. They provide mock data patterns and infrastructure guidance to ensure codebase stability as features grow across the application.

What is the best way to test partner-sync scenarios and daily streak logic?

Mock data patterns supply test infrastructure guidance by simulating psychology-based personalization and partner-sync scenarios. They establish clear expectations and decision criteria to determine when tests should be added alongside feature code.

Does Vitest work with Playwright for end-to-end integration testing?

Tests should be created alongside new features by following example workflows that draft and execute a comprehensive test plan. Starting with an end-to-end Playwright workflow validates critical user flows and establishes edge-case coverage.

Why does my daily streak logic fail during resets in testing?

Testing standards are needed for Sparq features to keep the codebase stable as features grow. Establishing rigorous patterns for E2E, unit, and integration tests catches regressions early and provides guidance for complex personalization scenarios.