laravel-integration-fakes

Create Laravel-native integration fakes with contracts, container bindings, and facades.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/edstevo/standards --skill laravel-integration-fakes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-integration-fakes
Source: https://github.com/edstevo/standards/tree/main/resources/boost/skills/laravel-integration-fakes
Command: npx skills add https://github.com/edstevo/standards --skill laravel-integration-fakes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables the creation of robust, Laravel-native "integration fakes" for your application's external dependencies, preventing accidental real-world calls during testing and providing clear assertion capabilities.

Core Features & Use Cases

  • Contract-Based Fakes: Design in-memory fakes for services like couriers, payment gateways, or APIs.
  • Assertion Helpers: Easily verify that specific integrations were called with the correct parameters.
  • Seeded Responses: Provide predictable responses or exceptions for tests.
  • Use Case: In your feature tests, ensure your order processing system correctly dispatches notifications via a fake courier service without actually sending emails or making API calls.

Quick Start

Use the laravel-integration-fakes skill to create a fake courier router for testing.

Frequently Asked Questions about laravel-integration-fakes

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

FAQPage Schema
How do I prevent accidental real API calls during Laravel integration testing?

Integration fakes prevent accidental real API calls during Laravel testing by using in-memory replacements bound via contracts and facades. This ensures tests remain deterministic and isolated from real-world interactions.

What is a contract-based fake in Laravel?

A contract-based fake in Laravel is an in-memory replacement implementing a shared interface for an external service. It uses container bindings and facades to intercept calls, enabling deterministic testing without real-world interactions.

How do I assert that my Laravel application called a fake service with correct parameters?

You assert application calls using built-in assertion helpers provided by the integration fake. These helpers record incoming calls and verify that specific integrations were executed with the exact expected parameters during testing.

Can I seed predictable responses or exceptions for external services in Laravel tests?

Yes, Laravel integration fakes support seeded responses and exceptions. This provides predictable outputs for tests, ensuring your application handles both successful interactions and expected failures deterministically.

Does this approach work for testing payment gateways and courier integrations in PHP?

Yes, this approach works for testing payment gateways and courier integrations in PHP. You design in-memory fakes based on service contracts, preventing actual API calls while providing clear assertion capabilities.

What is the best way to isolate external dependencies in Laravel feature tests?

The best way to isolate external dependencies in Laravel feature tests is using integration fakes. By binding in-memory replacements to contracts via the container, you prevent real-world interactions and gain call recording for reliable assertions.