skills.rest
veerababumanyam
veerababumanyamCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

testing

Define testing standards for RawDrive across frontend, backend, and AI service.

Updated Dec 17, 2025
Search Tags:#testing#pytest#Vitest#fixtures#unit-tests#integration-tests#test-coverage
One-click install
npx skills add https://github.com/veerababumanyam/RawDrive102 --skill testing-veerababumanyam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/veerababumanyam/RawDrive102/tree/main/.claude/skills/testing
Command: npx skills add https://github.com/veerababumanyam/RawDrive102 --skill testing-veerababumanyam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

RawDrive projects often diverge in testing strategies, which can lead to flaky releases and unclear quality signals. This Skill codifies testing standards across frontend, backend, AI service, and shared packages to ensure consistent, reliable tests throughout the codebase.

Core Features & Use Cases

  • Test Stack Guidance: Frontend uses Vitest + React Testing Library; Backend uses pytest + pytest-asyncio; AI Service uses pytest; Shared packages use Vitest + parity checks.
  • Directory & Workflow Standards: Prescribed locations for tests (e.g., frontend/src/test/, backend/tests/, services//tests/, packages//tests/).
  • Quality Assurance & Onboarding: Clear conventions for naming, fixtures, coverage targets, and cross-team parity checks to accelerate onboarding and maintainability.

Quick Start

Follow the standard testing guidelines to validate your changes. Run frontend tests with npm test in the frontend, run backend tests with pytest in the backend, and run AI service tests with pytest in services/ai-service. Use the recommended coverage targets and parity checks to ensure consistency across stacks.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I standardize testing across frontend and backend stacks?▼

Testing standards for frontend and backend stacks are defined by prescribing specific tooling like Vitest and pytest, setting directory structures, and enforcing fixture usage. This ensures consistent test coverage and reliable quality signals across different project environments.

What is the recommended test stack for frontend and backend applications?▼

The recommended test stack uses Vitest with React Testing Library for frontend, pytest with pytest-asyncio for backend, and Vitest with parity checks for shared packages. This combination ensures comprehensive test coverage and consistent quality assurance across all project layers.

How do I run unit and integration tests for different project services?▼

Run unit and integration tests by executing npm test in the frontend directory and pytest in the backend or services/ai-service directories. Following these prescribed workflow standards validates changes and maintains consistent test coverage across different application layers.

Does this testing approach work with both Vitest and pytest environments?▼

Yes, this testing approach works with both Vitest and pytest environments by providing stack-specific guidance. Frontend and shared packages use Vitest, while backend and AI services use pytest, ensuring tailored test execution and appropriate fixture management for each environment.

Why do I need directory and workflow standards for test coverage?▼

Directory and workflow standards for test coverage are needed to prevent divergent testing strategies that cause flaky releases and unclear quality signals. Prescribed test locations like frontend/src/test/ and backend/tests/ accelerate onboarding and maintain consistent quality assurance across teams.

Related Skills

Explore More Software Engineering Skills→
dorriodorrio

ln-743-test-infrastructure

Configure Vitest, xUnit, and pytest test environments for multi-language projects.

Community
Intermediate
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
RUSHYOPRUSHYOP

python-testing

Automate Python testing workflows with TDD, fixtures, mocks, and coverage targets.

Community
Advanced
linguistic76linguistic76
2

pytest

Test Python applications in SKUEL with pytest-asyncio and Result[T] assertions.

Community
Intermediate