665,000+ skills indexed

php-testoOFFICIAL

Explore all skills by this author →

Verified:Website GitHub

testo-migrate-from-phpunit

Migrates PHPUnit test suites to Testo's attribute-based format using predefined mappings and hybrid Rector/AI rewriting.

203|12|Updated Oct 12, 2025

Search Tags:#automated testing #test migration #test conversion #PHPUnit to Testo #attribute-based testing

One-click install

npx skills add https://github.com/php-testo/testo --skill testo-migrate-from-phpunit

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: testo-migrate-from-phpunit
Source: https://github.com/php-testo/testo/tree/main/skills/testo-migrate-from-phpunit
Command: npx skills add https://github.com/php-testo/testo --skill testo-migrate-from-phpunit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires rector, testo, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the migration of PHPUnit test suites to Testo, a modern testing framework, streamlining the process from a traditional class-based structure to an attribute-based approach.

Core Features & Use Cases

Automated Migration: Convert PHPUnit test cases to Testo's style with minimal manual intervention.
Approach Selection: Offers two approaches: Rector-assisted for mechanical tasks and AI-agent rewrite for complex scenarios.
Use Case: Ideal for developers looking to transition from PHPUnit to Testo, especially when dealing with complex test cases that require significant manual work for conversion.

Quick Start

Run the migration by invoking the testo-migrate-from-phpunit skill with the scope of tests you wish to convert.

Frequently Asked Questions about testo-migrate-from-phpunit

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

FAQPage Schema

How do I migrate PHPUnit test suites to an attribute-based testing style?▼

You can migrate PHPUnit test suites to attribute-based testing by using predefined mappings to convert test cases. This process uses Rector for mechanical changes and AI-agent rewriting for complex structural modifications.

What is the best way to convert complex PHPUnit test cases to Testo?▼

Converting complex PHPUnit test cases to Testo is best handled by an AI-agent rewriting approach. This manages significant structural changes that go beyond mechanical conversion capabilities.

Does the PHPUnit to Testo migration use Rector for test conversion?▼

Yes, the test migration from PHPUnit to Testo uses Rector for mechanical conversion of test cases. For complex structural changes, an AI-agent rewriting approach is applied instead.

Can I automate the transition from class-based PHPUnit tests to attribute-based testing?▼

Yes, automating the transition from class-based PHPUnit tests to attribute-based testing is possible. The migration uses predefined mappings with Rector and AI-agent rewriting to convert test classes automatically.

When should I use AI-agent rewriting instead of Rector for PHPUnit test migration?▼

AI-agent rewriting is used for PHPUnit test migration when complex test cases require significant structural changes. Rector is reserved for mechanical conversion tasks that follow predefined mappings.

Related Skills

Explore More Software Engineering Skills→

typo3-rector

Apply Rector-based refactorings to migrate TYPO3 extensions from v13 to v14.

testo-write-tests

Automate test case creation for the Testo PHP testing framework.

rector-developer

Create PHP transformation rules that traverse the PHP-Parser AST and return modified nodes.

php-best-practices

Automate PHP 8.2+ modernization and PSR-12 compliance via Rector.