PART 1: Hobobiker Rides Again: Plan It, Test It, Migrate It — Road Test: Having Claude Write the Tests Before the Trip

​Hobobiker Rides Again: Plan It, Test It, Migrate It

After Jamie Abrahams showed us a static-site-to-Drupal CMS migration with evals, DDEV lead maintainer Randy Fay tried the approach on his own very old Drupal 6 site, hobobiker.com. The results made one thing clear: Claude does its best work with a guided plan, a clear view of the source and destination, and success criteria it must prove it has met. In this three-part live series, Randy and the AI Learners Club take hobobiker.com on two different journeys. One ends in static HTML and the other in Drupal 11, and both are checked against the same set of tests. These are working sessions, so bring your questions, suggestions, and opinions. The peanut gallery is part of the show.

PART ONE: Road Test: Having Claude Write the Tests Before the Trip

​Before any migration starts, we need a way to know whether it worked. In this session, Randy works with Claude to explore hobobiker.com, a Drupal 6 site with years of content, and design automated tests that check both content and design: pages, paths, images, menus, and how things look. The goal is a test suite that doesn't depend on any particular destination, so we can run the same tests against a static archive and a Drupal 11 rebuild. Along the way, we'll look at how to push Claude past "looks good to me" toward a complete verification plan, and how a sandboxed environment like coder.ddev.com makes the whole process smoother.

​Don't miss the next session: The Last Ride: Sending a Drupal Site into Retirement!