Test Flow Diagram

Test Flow Diagram,

The image below is a flow diagram for testing the action of firing a weapon on Counter-Strike: Global Offensive.

Task 1G - Bug / Defect Summary Report

Smoke Grenade

Games Tester
Daniel Shepherd

Date of Test
15/06/2017

Versions
PC, Windows 10
Counter-Strike: Global Offensive.

Defect Description
When I enter the smoke, I could see my player model.

Severity
Trivial

Steps to Reproduce
1. Select the smoke grenade
2. Throw the grenade using MouseButton1
3. Walk into the smoke

Actual Behaviour
Whilst in the smoke screen, you can see your player model. It is very visible

Expected Behaviour
I expected to see nothing but smoke on the screen.

Evidence
The evidence is in this file, TEST_SUITE. A Screenshot is below;


Workaround
I couldn’t find a workaround for this defect.

Task 1F (C) - Test Suite

Test Suite,

The image below shows you the Test Suite table I made, testing the game, Counter-Strike: Global Offensive.

During this Test Suite, I was playing the map Cobblestone.


Task 1F (B) - Combinatorial Testing

Combinatorial Table,

The table below shows you my attempt at combining different actions at the same time to see if it would work or not. I tested these out on the game, Counter-Strike: Global Offensive.


Task 1F (A) - Data Dictionary

Data Dictionary,

The image below shows you an Excel document showing all the data for the game Counter-Strike: Global Offensive;


Task 1E - Game Test Processes

Game Test Processes and Description also Phase (Numbered),


Black Box Testing - Phase 1,

Black Box Testing focuses on testing the functionality and the inputs and outputs without focusing on the internal code.

White Box Testing - Phase 2,

Testing the game and its structure. You test the software and how it works as opposed to its functionality like Black Box Testing.

Smoke Testing - Phase 3,

The producer builds an updated version of the game, as many of the defects found last time are fixed. The first test on the new build is the Smoke Test. The test is to make sure everything loads ok. After it seems to work okay, it has passed the Smoke Testing.

Clean Room Testing - Phase 4,

Testing the way the player test’s the game. You focus on actually playing the game but with the main goal of finding and exploiting bugs so they can be fix.

Play Testing - Phase 5,

Play testing is where you launch software but don’t necessary ‘play’ it. Windows for example, play testing would be the launch of the windows.

Ad Hoc Testing - Phase 6,

This testing is only run once unless a defect has been found. If a defect has been found, the tester will attempt to replicate the defect on another level to see if it happens again. This test is the least formal test.

Task 1D - Game Test Phases

Game Test Phases and Description also the Phase of Testing (Numbered),


Preparation - Phase 1,

In this phase, you can plan out how much testing you will need in the future stages off your game.

Alpha - Phase 2,

Alpha is a very early version of the game. You would get testers to fill out a checklist making sure the product is meeting all the requirements.

Beta - Phase 3,

The Beta stage is to test the game for any problems/bugs that you can find. Once found these bugs should be fixed.

Gold - Phase 4

This stage happens at the end of the Beta stage. There is a Release Candidate of the game. All severity 1 bugs are fixed. 90% of severity 2 bugs are fixed. 85% of severity 3 bugs are fixed. Also the performance of the game matches the release expectation.

Certification - Phase 5,

Certification tests the game to see if it meets the platform technical requirements checklist (TRC). If it does then it passes and can be released. If not developers must make changes and resubmit the game.

Regression - Phase 6,

Regression Testing verifies that the game developed and tested previously still preforms fine after being changed/modified. Changes include patches software enhancements etc…