skills.rest
myeohVmzrka92
myeohVmzrka92COMMUNITY
Explore all skills by this author →
GitHub

testing-strategies

Define a 3-tier pytest testing strategy for Kailash applications.

Updated Apr 2, 2026
Search Tags:#testing#quality assurance#ci/cd#pytest#integration tests#e2e#real infrastructure
One-click install
npx skills add https://github.com/myeohVmzrka92/disease-risk-controller-S2 --skill testing-strategies-myeohvmzrka92
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-strategies
Source: https://github.com/myeohVmzrka92/disease-risk-controller-S2/tree/main/.claude/skills/12-testing-strategies
Command: npx skills add https://github.com/myeohVmzrka92/disease-risk-controller-S2 --skill testing-strategies-myeohvmzrka92

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams design a dependable testing approach for Kailash applications so unit, integration, and end-to-end coverage stays clear, consistent, and less dependent on fragile mocks.

Core Features & Use Cases

  • 3-Tier Test Strategy: Separates fast unit tests from integration tests and end-to-end tests.
  • Real Infrastructure Policy: Recommends using real databases, APIs, file systems, and LLM calls for higher-tier validation.
  • Use Case: A developer can use this Skill to organize pytest suites, choose when mocking is appropriate, and build fixtures for database-backed and API-backed workflows.

Quick Start

Use the testing-strategies skill to design a 3-tier pytest plan for my application and show me which tests should use real infrastructure.

Frequently Asked Questions about testing-strategies

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

FAQPage Schema
How do I structure pytest tests for integration and e2e workflows?▼

Structure pytest tests using a 3-tier strategy that separates fast unit tests, integration tests, and end-to-end tests, ensuring clear coverage and consistent design across database-backed components and API integrations.

When should I use real infrastructure instead of mocks in integration tests?▼

Use real infrastructure for integration and end-to-end tests by provisioning actual databases, APIs, file systems, and LLM calls rather than mocks, which removes guesswork and provides higher-tier validation for complex workflows.

What is the best way to organize a 3-tier testing strategy for Kailash applications?▼

The best way to organize a 3-tier testing strategy is to enforce structured fixtures, timeout management, and cleanup discipline while applying clear rules for when mocking is allowed across unit, integration, and end-to-end tiers.

Does the testing strategy work with LLM-driven agents and API integrations?▼

Yes, the testing strategy explicitly applies to LLM-driven agents and API integrations, requiring real infrastructure for higher-tier validation to ensure full user journey accuracy across these components.

Why do my mocked integration tests fail to catch real database and API errors?▼

Mocked integration tests fail because they bypass real infrastructure interactions; adopting a real infrastructure policy for integration and e2e tests validates actual database, API, and file system behavior directly.

Related Skills

Explore More Software Engineering Skills→
oimiragieooimiragieo
36

test-generator

Generate unit, integration, API, and E2E tests from specifications and components.

Community
Intermediate
aliciaplsaliciapls

testing-strategies

Design a 3-tier testing strategy for Kailash applications with real infrastructure guidance.

Community
Advanced
XSpoonAiXSpoonAi
17

spoonos-testing-patterns

Automates SpoonOS agent testing with pytest suites, mock LLM fixtures, and debugging workflows.

Official
Advanced
clowaclowa
1

terraform-test

Execute unit tests against Terraform modules without provisioning real infrastructure.

Community
Advanced