Objective

Confirm the readiness of the new website to replace the legacy version. Pixel-perfect and functional replication of the old Ruby website is not the goal.

What to do

• Verify the completeness of entity and content migration according to the migration list.
• Compare the selection of materials and media with the legacy source.
• Test new templates, navigation, forms, and key user scenarios.
• Check the SEO map of important URLs and 301 redirects.
• Check sitemap, robots, canonical tags, and main metadata.
• Test responsiveness and technical errors.
• Do not consider differences from the old interface as defects if the new implementation complies with the target design and functional requirements.

Result

The new version is confirmed as a standalone working website and is ready to completely replace the Ruby implementation.

Readiness criteria

• Data and media have been migrated in the agreed-upon scope.
• Key scenarios are working.
• Important old URLs are handled correctly.
• There are no blocking errors before switching.