Designing Tests for Computer Games

    PEARSON EDUCATION LTD
    Vocational

    This subtopic focuses on the systematic approach to identifying and documenting defects in computer games through structured testing. Learners will explore common defect types, test phases, and processes, and apply this knowledge to design a test suite and produce professional bug reports. Practical application includes creating test cases that cover functional, usability, and performance issues, ensuring quality assurance in game development.

    5
    Learning Outcomes
    4
    Assessment Guidance
    4
    Key Skills
    4
    Key Terms
    4
    Assessment Criteria

    Assessment criteria

    Pearson BTEC Level 3 Subsidiary Diploma in Creative Media Production (QCF)

    Learning Objectives

    What you need to know and understand

    • Identify and classify common defect types in game builds
    • Explain the purpose and sequence of test phases in a test programme
    • Design a comprehensive test suite covering functional and non-functional requirements
    • Produce a detailed bug report using a test suite
    • Evaluate the effectiveness of a test suite in detecting defects

    Assessment Criteria

    Key criteria assessors look for in your portfolio

    • Award credit for correctly identifying defect types (e.g., graphical, gameplay, audio, performance) with examples
    • Award credit for demonstrating understanding of test phases (e.g., alpha, beta, certification) and their objectives
    • Award credit for designing a test suite that includes test cases with clear steps, expected results, and pass/fail criteria
    • Award credit for producing a bug report that includes severity, priority, reproduction steps, and supporting evidence (screenshots/logs)

    Assessment Guidance

    Guidance for achieving higher grades

    • 💡Use industry-standard terminology (e.g., 'crash', 'soft lock', 'exploit') when describing defects
    • 💡Structure your test suite with a logical hierarchy (e.g., by module, feature, or test type)
    • 💡Always include edge cases and boundary values in your test cases
    • 💡In bug reports, state the environment (platform, build version) and attach visual evidence

    Common Mistakes

    Common errors to avoid in your coursework

    • Confusing defect severity with priority
    • Omitting negative test cases (testing invalid inputs)
    • Writing bug reports without clear reproduction steps
    • Failing to link test cases to specific requirements or user stories

    Pass / Merit / Distinction Evidence Checklist

    How your portfolio evidence is graded for PEARSON EDUCATION LTD Designing Tests for Computer Games

    Every vocational unit is marked against named criteria rather than an exam percentage. Your tutor's brief lists the exact codes for this unit — here is what each band is asking you to do.

    Pass (P)

    Demonstrate baseline knowledge, accurate terminology, and core practical application.

    Merit (M)

    Provide detailed analysis, structured explanations, and clear workplace reasoning.

    Distinction (D)

    Deliver thorough evaluation, original problem solving, and fully justified recommendations.

    Coursework AI Review

    Paste your assignment brief and check your draft against its P/M/D criteria

    Key Terminology

    Essential terms to know

    • Defect types and classification
    • Test phases and lifecycle
    • Test suite design principles
    • Bug reporting and documentation

    Ready to learn?

    AI-powered learning tailored to this unit