mocking-strategy-roster

Resolve mocking strategies and stack adapters for integration tests.

8|2|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill mocking-strategy-roster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mocking-strategy-roster
Source: https://github.com/SebastienDegodez/skraft-plugin/tree/main/plugins/skills/mocking-strategy-roster
Command: npx skills add https://github.com/SebastienDegodez/skraft-plugin --skill mocking-strategy-roster

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps agents to determine the appropriate mocking strategy and stack adapter for an integration test, ensuring the right tools are used without hardcoding.

Core Features & Use Cases

  • Mocking Strategy Resolution: Automatically resolves the mocking strategy (defaulting to Microcks) and the stack, then points to the concrete adapter.
  • Adapter Loading: Loads the matching adapter for the resolved strategy and stack.
  • No Hardcoded Approaches: Ensures no agent hardcodes a mocking approach, maintaining flexibility and consistency.

Quick Start

Load the 'mocking-strategy-roster' skill to resolve the mocking strategy for your integration test.

Frequently Asked Questions about mocking-strategy-roster

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

FAQPage Schema
How do I choose a mocking strategy for integration testing without hardcoding approaches?

Mocking strategy resolution automates selecting the appropriate mocking strategy and stack adapter for integration tests, defaulting to Microcks. It provides a resolution table for strategy and stack combinations to ensure flexibility and consistency without hardcoding.

What is the best way to resolve stack adapters for integration test mocking?

Adapter loading automatically matches and loads the correct stack adapter for your resolved mocking strategy. It uses a resolution table to map strategy and stack combinations, pointing directly to the concrete adapter needed for your integration tests.

Can I use Microcks for mocking strategy resolution in integration tests?

Microcks is supported as the default mocking strategy for integration tests. The resolution process automatically selects Microcks and loads the corresponding stack adapter, while also supporting in-process libraries for alternative scenarios.

When do I need a mocking strategy resolution table for software testing?

A mocking strategy resolution table is needed when managing multiple integration test stacks and strategies. It prevents hardcoded mocking approaches by systematically mapping strategy and stack combinations to their concrete adapters, maintaining testing consistency.

Does mocking strategy resolution work with in-process libraries?

In-process libraries are fully supported alongside Microcks for mocking strategy resolution. The system resolves the appropriate strategy and loads the matching adapter, accommodating both external service mocking and in-process testing libraries.