Lecture 7: Game Testing and Quality Assurance

Introduction to Game Testing and Quality Assurance

• Game testing ensures the quality and reliability of video games.
• Quality Assurance (QA) focuses on preventing defects throughout development.
• Testing verifies both functionality and player experience.
• The gaming industry demands rigorous testing standards due to complexity.
• Game testing encompasses technical, visual, and gameplay aspects.

Key terms: Quality Assurance

Importance of Game Testing in Development

• Game testing reduces the risk of bugs and errors at launch.
• A well-tested game enhances user satisfaction and trust.
• Testing ensures compliance with platform and legal standards.
• Monetization strategies rely on smooth gameplay and usability.
• Player retention is linked heavily to perceived polish and quality.

Key terms: Player Retention

Overview of Game Testing Methodologies

• Black-box testing evaluates functionality without knowing internal code.
• White-box testing focuses on examining code logic and structures.
• Grey-box testing combines black- and white-box approaches.
• Alpha testing is an internal method used in early development stages.
• Beta testing invites external participants to provide user feedback.

Key terms: Beta Testing

Types of Game Testing: Functional Testing

• Focuses on verifying that game mechanics work as intended.
• Involves script-driven test cases and real-time feedback.
• Replicates actual gameplay interactions.
• Critical for identifying game-breaking bugs.
• Often segmented to cover distinct gameplay loops or features.

Key terms: Game-breaking Bugs

Identifying Bugs: Common Techniques

• Error guessing based on experience identifies likely faults
• Boundary value analysis tests edge cases
• Exploratory testing discovers unforeseen issues
• Regression testing ensures new updates don’t break functionality
• Unit testing isolates smallest code units to uncover issues

Key terms: Boundary Value Analysis

Bug Reporting: Best Practices

• Write clear and concise titles for bug reports
• Include detailed reproduction steps
• Provide screenshots or video evidence
• Tag the severity and priority levels of bugs
• Ensure all reports are retrievable and filed correctly in tracking systems

Key terms: Severity

Tools for Bug Tracking and Management

• Jira is widely used for detailed bug tracking
• Bugzilla specializes in open-source project issues
• Trello suits smaller team projects
• GitHub Issues integrates with collaborative code management
• MantisBT is lightweight but efficient for defect tracking

Automated Testing in Game Development

• Automated testing covers repetitive and exhaustive tasks
• Catches scalability and performance issues in large games
• Tools like Selenium, Unreal Engine’s Automation Framework enable automation
• Can perform stress testing for system overload scenarios
• Reduces human error and increases testing efficiency

Key terms: Stress Testing

Case Study: Successful Game Testing Implementation

• Examining a case study from a AAA game studio
• Highlighting pre-launch testing strategies
• Emphasizing the role of regression testing
• Detailing the use of QA teams and testing tools
• Outcomes: Reduced post-launch bugs and improved player satisfaction

Key terms: Regression Testing

Real-World Applications of Game Testing

• Testing for cross-platform compatibility
• Catch issues specific to devices and systems
• Stress testing under high server loads
• Simulating player behavior across networks
• Preventing game-breaking exploits or cheats

Key terms: Stress Testing

Performance Optimization Testing

• Evaluate game performance under varied loads
• Identify bottlenecks impacting game speed and stability
• Test frame rates, memory usage, and asset loading times
• Use load testing to simulate thousands of users
• Incorporate stress testing for hardware resource limits

Key terms: Load Testing, Stress Testing

Game Testing Life Cycle: Phases Explained

• Requirement Analysis phase defines testing goals
• Test Planning outlines methodology and resources
• Test Case Development prepares test scenarios
• Test Execution validates functionality and identifies bugs
• Defect Reporting and Tracking logs and monitors issues

Key terms: Test Life Cycle

References

• Perry, S.P. (2005) Effective Methods for Software Testing. 3rd edn. Wiley.
• McGonigal, J. (2011) Reality Is Broken. London: Vintage.
• Schuh, P. (2004) Integrating Testing and Design. Boston: Pearson Education.
• Rogers, S. (2014) Level Up! The Guide to Great Video Game Design. Chichester: Wiley.
• Whittaker, J.A. (2002) How to Break Software: A Practical Guide to Testing. Addison-Wesley.
• Black, R. (2009) Managing the Testing Process. 3rd ed. Wiley.
• Kaner, C., Bach, J. and Pettichord, B. (2002) Lessons Learned in Software Testing. Wiley.
• Nguyen, H.Q. (2009) Automated Testing Handbook. 2nd ed. Redmond: Microsoft Press.
• Griesemer, R. (2016) Game QA: Lessons from AAA Studios. Developer Talks.
• Schreier, J. (2020) Press Reset. NYC: HarperCollins.
• Jains, R. (1991) The Art of Computer Systems Performance Analysis. New York: John Wiley & Sons.
• Whittaker, J.A. (2000) 'What is software testing? And why is it so hard?' IEEE Software.
• Kasurinen, J., & Smolander, K. (2014). What do game developers test in their products? IEEE Software.
• Pressman, R. (2014). Software Engineering: A Practitioner's Approach.
• Kent, A. (2005). The Complete Guide to Game Testing.
• Myers, G. (2011). The Art of Software Testing.
• Kaner, C. et al. (2003). Testing Computer Software.
• Tariq, F. (2020) Software Testing and Development Process. San Francisco: O'Reilly Media.
• McElroy, J. (2021) Game Feedback and Usability Testing. Cambridge: Academic Press.
• Bethke, E. (2012) Game Development and Production. 2nd edn. Cengage Learning.