Testing Workflow FAQs

Question 1

When should I use this skill?

Accepted Answer

Use this skill whenever you need to validate new code, debug test failures, ensure your work meets coverage requirements, or fix issues identified by mutation testing. It is the primary tool for ensuring code quality before committing changes.

Question 2

What specific testing capabilities does it provide?

Accepted Answer

This skill executes tests using PHPUnit for unit and integration testing, Behat for E2E scenarios, and Infection for mutation testing. It also promotes best practices like using Faker for dynamic test data generation to create more robust tests.

Question 3

What does the Testing Workflow skill do?

Accepted Answer

This skill automates running a comprehensive suite of tests, including unit, integration, E2E, and mutation tests. It validates code changes and enforces strict quality gates like 100% code coverage and a 100% Mutation Score Indicator (MSI).

Question 4

How does this skill improve my AI coding workflow?

Accepted Answer

It provides a structured, command-based workflow (e.g., `make all-tests`) for testing, which saves time and reduces manual errors. By enforcing quality gates automatically, it ensures that only high-quality, thoroughly tested code gets integrated.

Testing Workflow

Key Features

Use Cases

Testing Workflow

Key Features

Use Cases