migration-test

Seeds SchedulePress fixtures on master, switches branches, and verifies post-migration cron behavior.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/nahidthenh/wpsp-docker-e2e --skill migration-test-nahidthenh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migration-test
Source: https://github.com/nahidthenh/wpsp-docker-e2e/tree/main/.claude/skills/migration-test
Command: npx skills add https://github.com/nahidthenh/wpsp-docker-e2e --skill migration-test-nahidthenh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Testing whether SchedulePress scheduling features survive a code migration is slow and error-prone: you must seed posts on master, wait for their scheduled times, switch branches, trigger WP-Cron, and manually compare every post status. This Skill automates that entire cycle and produces a Pass/Fail report. ## Core Features & Use Cases - Automated fixture seeding: Creates 7 test posts covering Standard Schedule (post/page), Advanced Schedule, Republish, Unpublish, Auto-Schedule, and Manual Schedule via WP-CLI. - Timed branch migration: Uses a 10-minute scheduled wakeup to switch both free and PRO plugins from master to a feature branch, then triggers WP-Cron twice for the PRO two-step hook chain. - Structured Pass/Fail report: Compares actual post statuses against expected outcomes, audits WPSP cron hooks, and lists failures with manual-intervention steps. - Use Case: Before merging a SchedulePress feature branch, run the migration test to confirm that posts scheduled under master still publish, republish, or unpublish correctly after the branch switch. ## Quick Start Run /migration-test with the feature branch name, for example asking to run the migration test against branch fix/schedule-bug.

Frequently Asked Questions about migration-test

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

FAQPage Schema
How do I test SchedulePress migration between branches?

Run /migration-test with the target branch name. The skill seeds 7 scheduled fixtures on master, waits 10 minutes, switches both free and PRO plugins to the branch, triggers WP-Cron, and reports Pass/Fail per feature.

How to verify WordPress scheduled posts still publish after a code change?

Seed posts with post_status=future and a near-future date via WP-CLI, switch the plugin code, then run WP-Cron and compare each post's status against the expected outcome. This skill automates that full sequence.

Does the migration test require the SchedulePress PRO plugin?

The PRO plugin is optional. If wp-scheduled-posts-pro is inactive, the PRO-only tests (Advanced Schedule, Republish, Unpublish) are marked as SKIP with a note, while the free-plugin tests still run.

Why do republish and unpublish tests need WP-Cron run twice?

PRO republish and unpublish use a two-step hook chain, so a single cron run may not complete the transition. The skill runs cron twice with a 30-second gap to let the chained hooks fire.

What happens if the migration state file is missing during verification?

The verify phase depends on .migration-state.json for branch names and post IDs. If it is missing, the skill stops and asks you to re-run /migration-test from the beginning to reseed fixtures.