OVERVIEW

Activities in this unit of study are designed to introduce learners to quality and functionality assurance. This unit will focus specifically on the testing, troubleshooting, and debugging of an interactive application or video game

TOPICS

In this unit, learners will explore the following topics:

• Test teams (e.g. internal, external)
• Testing focus (e.g. usability, functionality, performance, load, build verification, game balance)
• Product testing procedures (e.g. alpha, beta)
• Defect tracking databases

LEARNING OBJECTIVES

By the end of this unit, learners should be able to perform the following tasks:

• Explain the importance of QA and testing
• Explain the importance of documentation during testing stages
• Explain the necessity of a defect tracking database
• Describe basic troubleshooting strategies
• Perform successful debugging and troubleshooting activities within a game environment
• Locate bugs within a game environment using debugging software tools

1. Overview of testing

• a. Purpose of testing
• b. Who does the testing
• c. When testing should be done

2. Verification versus validation

3. Relationship between testing, quality assurance, and quality control

4. Levels of software testing

• a. Functional i. Acceptance testing: alpha, beta

5. Non-functional

• a. Performance: load and stress testing
• b. Usability
• c. Security
• d. Portability

6. Testing Documentation: test plan, test cases/scenarios

7. Defect Tracking

• a. Parameters
• b. Defect life cycle

OUTLINE

1. Overview of testing
2. Purpose of testing
3. Who does the testing
4. When testing should be done
5. Verification versus validation
6. Relationship between testing, quality assurance, and quality control
7. Levels of software testing
8. Functional
9. Acceptance testing: alpha, beta
10. Non-functional
11. Performance: load and stress testing
12. Usability
13. Security
14. Portability
15. Testing Documentation: test plan, test cases/scenarios
16. Defect Tracking
17. Parameters
18. Defect life cycle