Unit 42 - Games Testing

Different Games Platforms - Games often Played

PC - Minecraft

Mobile - Angry Birds

Xbox One - Destiny

Xbox 360 - Super Meat Boy

Xbox - Need For Speed

Playstation - Oddworld

PS2 - Crash Bandicoot

PS3 - God of War

PS4 - The Last of Us

Nintendo DS - Mario Kart

Nintendo DSi - Animal Farm

Nintendo 3DS - Pokemon

Wii - Wii Sports

Wii U - Just Dance

Nintendo Switch - Splatoon 2

Input Method: Controller

What is a bug?

A bug (software-wise) is a problem or flaw within the game, whether it is a visual glitch or something in the code, mostly producing unexpected results or giving the players an advantage or an edge against the game and/or its players. Every game is bound to have a few.

Bug Report - Super Duper Lava Jump

Bug(s) Found: Player is apparently lava-proof and can walk on it.

To Be Able To: Understand the Various Aspects of the Gaming Sector - RED

Input Methods:

MicroPhone

Controller - Joystick, TouchPad, Motion Sensor, Balance Board, VR Controllers

Keyboard

Mouse

Display Types:

Computer Monitor

TV Screens - A larger screen allows for less clutter with an in-depth HUD in things like action games

Phone Screen

Dual Screens (Nintendo DS, Wii U, Switch) - More HUD Space, One is normally touch interactive, more dynamic gameplay in things like fast-paced Adventure Games.

VR Headset - Good for Horror, adds another fear factor

Projector

Write an article for Leaf Gaming Magazine, explaining different display and input types to a young gamer. This must be informative and compare and contrast the various aspects researched in today's lesson.

Quality Assurance

Understand quality assurance in the games industry.

Quality Assurance - When the quality of the game is maintained at a constant level throughout.

Brainstorming Elements in Pre-Production/Production/Post-Production of Games

Agile Development

Bug Reports from Professional Game Developers

Alpha/Beta/Early Release Test Versions

Smoothly responding to change and customer ideas

During the Testing Stage of Game Creation we look to:

Test all major/likely events
Grade the severity of an error
Have an organised approach to fixing errors

What is a Test Case in Bug Reporting?

A test of set conditions where a tester will determine whether or not the game functions and whether or not it needs fixing or improving.

Test Case Example

Test Suite ID	The ID of the test suite to which this test case belongs.
Test Case ID	The ID of the test case.
Test Case Summary	The summary / objective of the test case.
Related Requirement	The ID of the requirement this test case relates/traces to.
Prerequisites	Any prerequisites or preconditions that must be fulfilled prior to executing the test.
Test Procedure	Step-by-step procedure to execute the test.
Test Data	The test data, or links to the test data, that are to be used while conducting the test.
Expected Result	The expected result of the test.
Actual Result	The actual result of the test; to be filled after executing the test.
Status	Pass or Fail. Other statuses can be ‘Not Executed’ if testing is not performed and ‘Blocked’ if testing is blocked.
Remarks	Any comments on the test case or test execution.
Created By	The name of the author of the test case.
Date of Creation	The date of creation of the test case.
Executed By	The name of the person who executed the test.
Date of Execution	The date of execution of the test.
Test Environment	The environment (Hardware/Software/Network) in which the test was executed.