testing-strategies

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

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/aliciapls/ML-Week-2---Healthcare --skill testing-strategies-aliciapls
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-strategies
Source: https://github.com/aliciapls/ML-Week-2---Healthcare/tree/main/.claude/skills/12-testing-strategies
Command: npx skills add https://github.com/aliciapls/ML-Week-2---Healthcare --skill testing-strategies-aliciapls

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork from test planning by giving you a clear, enforceable strategy for organizing unit, integration, and end-to-end tests across Kailash applications.

Core Features & Use Cases

  • 3-Tier Test Design: Separates fast unit tests from higher-fidelity integration and end-to-end coverage.
  • Real Infrastructure Guidance: Recommends actual databases, HTTP services, file systems, and cached LLM calls for tiers 2 and 3.
  • Test Organization: Helps structure test suites, fixtures, timeouts, cleanup, and CI/CD execution paths.
  • Use Case: A team building a workflow-heavy healthcare app can use this Skill to decide what to mock, what to run against real services, and how to keep tests stable and realistic.

Quick Start

Use the testing-strategies skill to create a 3-tier testing plan for my project and recommend which parts should use real infrastructure versus mocks.

Frequently Asked Questions about testing-strategies

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

FAQPage Schema
How do I structure integration tests and end-to-end tests for workflow applications?

Structure integration and end-to-end tests using a 3-tier strategy that isolates fast unit tests, runs integration tests against real infrastructure like databases and HTTP services, and executes full end-to-end workflows with proper cleanup and timeout discipline.

What is the best way to organize unit tests versus integration tests in CI/CD pipelines?

The best way to organize tests in CI/CD is a 3-tier strategy: tier 1 uses mocking for fast unit tests, while tiers 2 and 3 run against real infrastructure to ensure higher-fidelity integration and end-to-end coverage with stable execution paths.

When should I use real infrastructure versus mocks for testing APIs and databases?

Use real infrastructure for integration and end-to-end tests in tiers 2 and 3 to validate actual database persistence, Nexus APIs, and HTTP services, restricting mocks to tier 1 unit tests to maximize both speed and test fidelity.

Does this testing strategy work with LLM-backed agents and cached API calls?

Yes, this testing strategy applies to LLM-backed agents by utilizing cached LLM calls within real infrastructure tiers, ensuring deterministic end-to-end and integration tests without sacrificing the reliability of the workflow execution.

How do I manage test cleanup and timeouts for real infrastructure integration tests?

Manage test cleanup and timeouts by applying timeout discipline and structured cleanup routines across tier 2 integration and tier 3 end-to-end tests, ensuring real infrastructure like DataFlow persistence and file systems remain stable.

What are the limitations of mocking in unit tests for complex workflow execution?

Mocking in unit tests provides speed but lacks fidelity for DataFlow persistence and Nexus APIs, which is why this testing strategy restricts mocks to tier 1 and mandates real infrastructure for integration and end-to-end coverage.