testing-strategies

Implement 3-tier unit, integration, and end-to-end tests for Kailash applications.

1|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/terrene-foundation/kailash-coc-claude-rs --skill testing-strategies-terrene-foundation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-strategies
Source: https://github.com/terrene-foundation/kailash-coc-claude-rs/tree/main/.claude/skills/12-testing-strategies
Command: npx skills add https://github.com/terrene-foundation/kailash-coc-claude-rs --skill testing-strategies-terrene-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework for testing Kailash applications, ensuring code quality and reliability through a structured 3-tier testing approach and a strict NO MOCKING policy for integration and end-to-end tests.

Core Features & Use Cases

  • 3-Tier Testing: Implements Unit, Integration, and End-to-End tests.
  • NO MOCKING Policy: Emphasizes testing with real infrastructure in Tiers 2 and 3 to uncover real-world issues.
  • Use Case: When developing a new feature, use this Skill's guidelines to write unit tests for individual components, integration tests that verify interactions with a real database, and end-to-end tests that simulate a full user workflow.

Quick Start

Follow the 3-tier testing strategy outlined in the documentation to ensure robust application quality.

Frequently Asked Questions about testing-strategies

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

FAQPage Schema
How do I set up integration testing for Kailash workflows without mocking?▼

Integration testing for Kailash workflows uses a strict NO MOCKING policy, requiring real databases and APIs to validate DataFlow and Nexus interactions. This approach uncovers real-world infrastructure issues that mocked tests miss. Tests are organized using pytest.

What is the 3-tier testing strategy and when do I need it?▼

The 3-tier testing strategy is a framework comprising unit, integration, and end-to-end tests for Kailash applications. You need it to ensure code quality and reliability by validating individual components, real database interactions, and full user workflows.

How do I write end-to-end tests that cover Kaizen agents and real infrastructure?▼

You write end-to-end tests using pytest to simulate full user workflows across real infrastructure, covering DataFlow, Nexus, and Kaizen agents. This ensures the entire Kailash application stack functions correctly under realistic conditions without mocks.

Can I use pytest with CI/CD pipelines for Kailash application testing?▼

Yes, pytest integrates with CI/CD pipelines to automate the 3-tier testing strategy for Kailash applications. This integration ensures unit, integration, and end-to-end tests run against real infrastructure continuously, maintaining code quality throughout development.

Why does my integration testing fail when using mocked databases instead of real ones?▼

Integration testing fails because the strategy enforces a strict NO MOCKING policy for Tiers 2 and 3. Using mocks bypasses real-world database and API interactions, preventing the discovery of infrastructure issues that real database testing is designed to uncover.

What's the best way to organize tests across unit, integration, and end-to-end tiers?▼

The best way to organize tests is following the 3-tier strategy: unit tests for individual components, integration tests for real database and API interactions, and end-to-end tests for full user workflows, all structured within pytest.