testing

name	testing
description	Guidelines for testing using Playwright and Chrome DevTools

Overview

Use Playwright MCP for end-to-end testing and Chrome DevTools for debugging. Follow page-specific test instructions in .github/instructions/page.<page-name>.instructions.md files for detailed testing procedures.

General Testing Workflow

• Start by navigating to the application URL
• Follow the test instructions for each page in the corresponding instruction file
• Use snapshots to verify UI state before and after interactions
• Check console messages for errors during testing
• Validate local storage changes when applicable

Page-Specific Testing Instructions

Refer to these instruction files for detailed test procedures for each page:

• page.home.instructions.md - Home page navigation and initial setup
• page.create-game.instructions.md - Game creation workflow
• page.saved-games.instructions.md - Saved games management
• page.custom-game-modes.instructions.md - Custom game modes handling
• page.play.instructions.md - Game playing interface
• page.game-summary.instructions.md - Post-game summary display
• page.campaign-games.instructions.md - Campaign games listing
• page.start-campaign.instructions.md - Campaign initialization
• page.continue-campaign.instructions.md - Campaign continuation
• page.campaign-upgrade.instructions.md - Campaign progression
• page.not-found.instructions.md - Error page handling

Testing Tools and Commands