What is the policy for newly discovered bugs?

The skill includes a general rule that if any error or bug is found, a corresponding test case must be created immediately to ensure future coverage.

Does this skill run tests automatically?

Yes, the skill instructs the Claude AI agent to run tests autonomously as part of the development workflow without requiring user intervention.

How does it handle UI changes and verification?

It mandates UI verification using the Chrome DevTools MCP and requires saving dated screenshots in the docs/screenshots directory for visual auditing.

Can it interact with the database during tests?

Yes, the skill utilizes the Supabase MCP for database interaction and verification, avoiding the need for local Supabase CLI installations.

Which E2E framework is supported by this skill?

It is specifically optimized for Playwright, including configurations for environment variables, headless browser management, and dev server connectivity.

LabTrack Testing Strategy

Name: LabTrack Testing Strategy
Author: mpaicoding-byte

bympaicoding-byte

Security & Testing

Standardizes multi-layer testing workflows including Playwright E2E, Vitest components, and automated UI verification.

About

This skill provides comprehensive guidance for maintaining code quality in the LabTrack project by automating unit, component, integration, and E2E testing workflows. It specializes in troubleshooting Playwright environment issues, enforcing UI verification through screenshots, and integrating with Supabase for backend testing without manual CLI intervention. By providing the AI agent with specific commands and error-handling patterns, it ensures autonomous validation of code changes and prevents regressions through a mandatory bug-to-test creation policy.

Key Features

Direct integration with Supabase MCP for database seeding and verification
Automated E2E testing with Playwright and environment-specific troubleshooting patterns
Multi-tier testing support covering Unit (Node), Component (Vitest), and Integration (Supabase)
0 GitHub stars
Mandatory UI verification using Chrome DevTools MCP with standardized screenshot archiving
Automated bug-to-test conversion policy to ensure regression coverage for reported issues

Use Cases

Executing full-stack E2E tests against a local dev server and remote Supabase instance
Performing visual regression checks and saving evidence to documented screenshot paths
Triaging test failures and automatically generating new test cases for identified bugs

About

Key Features

Direct integration with Supabase MCP for database seeding and verification
Automated E2E testing with Playwright and environment-specific troubleshooting patterns
Multi-tier testing support covering Unit (Node), Component (Vitest), and Integration (Supabase)
0 GitHub stars
Mandatory UI verification using Chrome DevTools MCP with standardized screenshot archiving
Automated bug-to-test conversion policy to ensure regression coverage for reported issues

Use Cases

Executing full-stack E2E tests against a local dev server and remote Supabase instance
Performing visual regression checks and saving evidence to documented screenshot paths
Triaging test failures and automatically generating new test cases for identified bugs