context-testing-infrastructure

Orchestrate tiered testing infrastructure for UI mocks, auth stubs, and full-stack tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/stars-end/affordabot --skill context-testing-infrastructure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-testing-infrastructure
Source: https://github.com/stars-end/affordabot/tree/main/.claude/skills/context-testing-infrastructure
Command: npx skills add https://github.com/stars-end/affordabot --skill context-testing-infrastructure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Building a robust and efficient testing strategy that balances speed, isolation, and comprehensive coverage can be challenging.

Core Features & Use Cases

  • Tiered Testing Strategy: Understand the three-tier E2E testing approach (UI Mock, Auth Stub, Full Stack) for optimal speed and isolation in your test suite.
  • Comprehensive Test Navigation: Locate Playwright E2E tests, Pytest backend tests, and various test utilities and fixtures for efficient test development.
  • Smoke Test & Configuration: Explore backend health checks and frontend smoke tests, along with Playwright and Pytest configurations, for quick validation.
  • Use Case: When a test fails or you need to implement a new test, this Skill provides context on existing test patterns, mocking strategies, and CI test configurations.

Quick Start

Ask about "test patterns" or "auth stub" to get context on the tiered testing strategy, fixtures, mocks, and test configurations.

Frequently Asked Questions about context-testing-infrastructure

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

FAQPage Schema
How do I set up a tiered testing strategy with Playwright and Pytest?▼

A tiered testing strategy uses three levels: UI mock tests for speed, auth stub tests for isolation, and full-stack tests for comprehensive coverage. This Skill orchestrates all three tiers, providing Playwright E2E configurations, Pytest fixtures, and mocking patterns to balance test speed with thorough validation across your stack.

What's the difference between UI mock, auth stub, and full-stack testing?▼

UI mock tests run frontend logic without backend calls for fastest feedback. Auth stub tests replace authentication with stubs for isolated integration testing. Full-stack tests exercise the entire application end-to-end. This Skill guides implementation of all three tiers to optimize speed, isolation, and coverage in your test suite.

How do I structure Playwright E2E tests with fixtures and mocks?▼

Playwright E2E tests use fixtures for setup and teardown, combined with mocking strategies to control external dependencies. This Skill provides existing test patterns, fixture configurations, and mock implementations that show how to structure tests at each tier and integrate them with CI pipelines.

Can I use Playwright and Pytest together in the same test infrastructure?▼

Yes. This Skill orchestrates both Playwright for UI-layer E2E tests and Pytest for backend-layer tests within a unified tiered infrastructure. Both frameworks are configured to work with shared mocking strategies, fixtures, and CI configurations for a cohesive testing approach.

How do I configure CI to run my tiered tests efficiently?▼

This Skill provides CI configurations optimized for tiered testing: running fast UI mock tests first for quick feedback, then auth stub tests, and full-stack tests last. Configuration examples show how to parallelize tiers, manage test isolation, and fail fast without sacrificing coverage.

What happens when a test fails—how do I debug across tiers?▼

When a test fails, this Skill provides context on existing test patterns, mocking strategies, and fixture setups to help you isolate the failure. It guides you to the relevant tier's configuration and logs, then shows similar passing tests and mock implementations to diagnose the issue quickly.