test-game

Manually test the Zatacka game in a browser and generate a structured bug report.

Updated Feb 7, 2026
One-click install
npx skills add https://github.com/darenhart/zataka-ts --skill test-game
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-game
Source: https://github.com/darenhart/zataka-ts/tree/main/.claude/skills/test-game
Command: npx skills add https://github.com/darenhart/zataka-ts --skill test-game

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to manually testing the Zatacka game, ensuring its functionality, performance, and stability across different configurations.

Core Features & Use Cases

  • Manual Testing: Execute a comprehensive checklist covering basic, gameplay, configuration, and edge case tests.
  • Bug Reporting: Facilitates detailed reporting of issues, including reproduction steps and severity.
  • Performance Validation: Assesses game performance metrics like FPS and input lag.
  • Use Case: After a new game mode is implemented, use this Skill to thoroughly test its behavior, responsiveness, and compatibility with various player counts before release.

Quick Start

Execute the manual test checklist for the Zatacka game in your browser.

Frequently Asked Questions about test-game

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

FAQPage Schema
How do I manually test a browser game for bugs and performance issues?

Manual browser game testing uses a structured checklist to identify bugs, performance issues, and edge cases. It covers gameplay mechanics and configuration options, generating a report of passed tests, observations, and metrics.

What should be included in a game QA checklist for browser gameplay?

A game QA checklist should include basic functionality, gameplay mechanics, configuration options, and edge cases. It validates performance metrics like input lag and generates a structured report with reproduction steps and severity levels.

How do I validate FPS and input lag during web game testing?

Web game testing validates FPS and input lag through performance assessment within the browser environment. It measures responsiveness across various player counts and configurations, documenting any performance degradation in the final report.

Can I use manual testing to check edge cases in multiplayer browser games?

Manual testing checks edge cases in multiplayer browser games by evaluating behavior, responsiveness, and compatibility with various player counts. It thoroughly tests new game modes before release to identify and report any issues.

What is the best way to report bugs found during browser game testing?

Browser game bug reporting facilitates detailed documentation of issues, including reproduction steps and severity. The structured report contains passed and failed tests, observations, performance metrics, and an overall game experience assessment.

Does game testing work without external dependencies or frameworks?

Game testing works without external dependencies, operating entirely within the browser environment. It requires no additional frameworks, utilizing references to execute the manual test checklist and generate the assessment report.