User:ScottLodge/sandbox

Quality Assurance Testing (Latin: jobofthagods) is a process implemented by software companies and games studios to help improve the overall quality of their products, to ensure the best possible product for the customers, clients and end users.

What does a tester do?

A tester's main function is to discover, reproduce and document any bugs that may appear in the software or game and report the findings to the relevant person or department.

“ So, you get paid to sit and play video games all day?? ” — Every person when I tell them what I do, 2019

Overview

The QA process seems relatively simple on the surface but really, it's quite the opposite. Often mistaken as "playing video games and getting paid" QA testing is far more in depth. Testers are both on the front line of the development of all software and games, but also the last line of defence. Working tirelessly to ensure that not only the product is delivered on time but also in most stable state possible.

The QA Tester Process

Testers work closely with production to put together a delivery calendar broken down into Sprints, which can be anything from 3 days to 3 months. This assists the QA department in establishing a testing timeline to ensure they can sufficiently test the feature. From there a test plan will be drawn up (or reused depending on the feature) and distributed between the testing team. This allows the testers a full coverage of possible tests, casting a wider net to catch as many bugs as possible. The testers will then methodically work their way through the plan, checking off each test as it passes or fails. Testers will utilise different forms of testing such as flow, exploratory, destructive, functionality, compatibility and extensive. When a bug is discovered, the magic begins. The tester will begin the documentation of the bug. Beginning the process by trying to reproduce the issue and establishing the severity of the issue. The severity can range from SS/A class which is reserved for the most heinous of bugs like crashes, then they flow through to B, C then D, which would be used for missing assets or small improvements needed. If the bug breaks the game in any way, either blocking the flow of progression, crashing, hanging or even bricking the device, then the issue needs to be reported to production and relevant department as soon as possible so they can formulate a plan for a fix. The bug logging then begins using project management/bug tracking software such as Jira. The tester will log extensive bug reports detailing as much as possible to allow full clarity of the issue for the assignee. Depending on the severity of the bug, the tester may be required to continue testing around the issue after logging to cover all possible impacted areas, depending on the complexity of the issue. Once the test plans have been completed by the testing team, bug regression begins. Any bugs logged and claimed fixed by the relevant departments now need to be retested to confirm the fix. Depending on length and depth of the sprint the whole process begins again with the next feature.

Why Follow This Process?

Making sure that the product arrives on time and in the best possible condition is the most important aspect of any kind of development, software, games or other. Processes such as this are in place to help achieve this goal on a daily basis. It allows for all departments full visualisation of the QA day to day and has helped the creative industries recognise Quality Assurance as an important role and a viable career option and not just a stepping stone for progression into other departments.