skills.rest
gmedia
gmediaOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Testing Strategy

Define standardized unit, feature, and end-to-end testing strategies with templates.

4|1|Updated Sep 25, 2025
Search Tags:#testing#templates#laravel#playwright#unit-testing#e2e-testing#feature-testing
One-click install
npx skills add https://github.com/gmedia/erp --skill testing-strategy-gmedia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Testing Strategy
Source: https://github.com/gmedia/erp/tree/main/.agent/skills/testing-strategy
Command: npx skills add https://github.com/gmedia/erp --skill testing-strategy-gmedia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Defines a standardized approach to creating unit, feature, and end-to-end tests that align with codebase patterns.

Core Features & Use Cases

  • MCP Tools integrated for debugging and test validation (e.g., mcp_laravel-boost_last-error, mcp_laravel-boost_read-log-entries, mcp_laravel-boost_database-query, mcp_laravel-boost_tinker, mcp_laravel-boost_browser-logs, mcp_filesystem_read_file).
  • Clear guidance on test types and file locations: tests/Feature, tests/Unit, tests/e2e.
  • Templates and patterns for writing tests across controllers, actions, requests, and Playwright e2e flows.

Quick Start

Follow the guide to start creating unit, feature, and e2e tests in the project today.

Frequently Asked Questions about Testing Strategy

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

FAQPage Schema
How do I standardize testing across Laravel and Playwright projects?▼

Standardized testing defines unit, feature, and e2e test placement alongside naming conventions and tooling references for Laravel and Playwright. This ensures consistent test quality, maintainability, and scalable patterns across the codebase.

What is the best way to structure feature tests and unit tests in a Laravel application?▼

Structuring feature tests and unit tests involves placing them in dedicated tests/Feature and tests/Unit directories. Applying standardized templates for controllers and actions ensures your Laravel application maintains scalable testing patterns.

How do I write end-to-end tests using Playwright for Laravel applications?▼

Writing end-to-end tests using Playwright involves placing e2e test flows in the tests/e2e directory. You can leverage MCP tools like browser-logs to read console outputs and validate application behavior during your Playwright e2e testing flows.

Can I use MCP tools for debugging and validating Laravel test failures?▼

Yes, you can use MCP tools for debugging Laravel test failures. Tools like mcp_laravel-boost_last-error, read-log-entries, database-query, and tinker allow you to query application state and validate test outcomes during debugging.

Does this testing strategy require specific dependencies to run unit and e2e tests?▼

No, this testing strategy does not require specific external dependencies to implement. It provides reusable guidance and templates referencing Laravel for unit/feature tests and Playwright for e2e tests without locking you into additional package requirements.

Related Skills

Explore More Software Engineering Skills→
oaustegardoaustegard
137

versioning-skills

Initialize Git repositories and commit changes for skill directories.

Community
Basic
DatTran26DatTran26

ck:test

Execute unit, integration, e2e, and UI tests with coverage reports.

Community
Advanced
DonaldMurilloDonaldMurillo
13

log-debug

Query GoFastr application logs and metrics via MCP tools.

Community
Intermediate
janhestersjanhesters

aidd-test-writing

Generate unit, functional, integration, and E2E tests using RITEway principles.

Community
Advanced