Skip to main content

Bug Detection & Workflow Integration

Bug Detection

Razer QA Co-AI supports bug detection in three main methods:

  1. Manual Reporting – Users can identify a bug and trigger a report directly via the web app.
  2. Performance Thresholds – The system automatically detects issues when metrics like CPU, GPU, RAM, or FPS exceed predefined limits.
  3. AI Analysis – AI models identify mismatches between expected gameplay behavior and actual in-game events. Note: This feature is not available to freemium users. Please contact our team at qac-support@razer.com to learn more.

When a bug is detected or reported, these actions are performed:

  1. A new bug entry is created
  2. The previous 20 seconds of play time are recorded and uploaded to the Web Application
  3. Bug characteristics are manually editable or pre-compiled by AI to characterize the bug

Workflow Integration

Razer QA Co-AI supports integration with Jira. To set up your Jira project, please follow these instructions.

Support for additional ticketing platforms is under consideration. We welcome your feedback to help shape future integrations.

Once an issue is reported via Razer QA Co-AI, you may create a ticket in Jira with just a click. All media (videos and screenshots) are stored in the web application and kept for 24 hours. To retain these files, we recommend creating a Jira ticket and saving the media there.

Bug types tracked by Razer QA Co-AI

Order by priorityBug TypeDescriptionExample(s)SupportedIn Development
1Crash/Freeze (Stability)Critical issues that render the game unplayable by causing crashes or hangs (e.g. game closing or not responding)N/A
2Performance IssuesProblems that degrade game performance, such as low frame rates, extreme lag, long load times, or memory leaksN/A
3Gameplay/Mechanics BugsFunctional bugs where game mechanics or features don’t work as intended, breaking game rules or logic
  • Enemy death still adds to timer
  • Health heals wrong value (25 instead of 20)
  • Ammo pickup gives wrong amount (35 instead of 30)
  • Enemies deal too much damage (10 vs 5)
4Collision/Physics GlitchesIssues with collision detection or physics that allow characters or objects to intersect or go places they shouldn’tN/A
5AI/NPC Behavior BugsProblems with enemy or NPC behavior not following intended design, leading to unpredictable or faulty actionsN/A
6Graphics/Visual GlitchesVisual errors or graphical defects such as missing/misaligned textures, screen tearing, or objects/characters appearing incorrectly in the worldN/A
7Audio BugsIssues with game sound or music, such as missing or delayed audio, sounds with wrong volume, or clips that play at incorrect times or loop improperlyN/A
8UI/UX IssuesUI problems that hinder the player experience – e.g. missing/misaligned UIN/A