Quick Navigation

QUALITY ASSURANCE (QA)#1

A systematic process ensuring that a product meets specified requirements and standards throughout development.

BUG REPORTING#2

The practice of documenting issues or defects found during testing, including details like severity, steps to reproduce, and screenshots.

PLAYTESTING#3

A method of testing where real users play the game to provide feedback on gameplay, usability, and overall experience.

TEST PLAN#4

A detailed document outlining the testing strategy, objectives, resources, schedule, and scope for a specific project.

AUTOMATED TESTING#5

Using software tools to execute pre-scripted tests on a software application before it is released.

MANUAL TESTING#6

The process of manually checking software for defects without the use of automation tools.

RISK-BASED TESTING#7

A testing approach that prioritizes testing efforts based on the risk of failure and its impact on the project.

DOCUMENTATION#8

Written records that detail the processes, procedures, and results of QA activities, aiding communication between teams.

TEST CASE#9

A set of conditions or variables under which a tester assesses whether a system or software application functions correctly.

USER FEEDBACK#10

Input and opinions from players regarding their experience with the game, used to improve quality and usability.

BUG TRACKING TOOLS#11

Software applications that help teams record, manage, and track defects and issues throughout the development lifecycle.

EXPLORATORY TESTING#12

An informal testing approach where testers explore the application without predefined test cases to discover defects.

PERFORMANCE TESTING#13

A type of testing that evaluates the speed, responsiveness, and stability of a software application under a particular workload.

AGILE DEVELOPMENT#14

A methodology that emphasizes iterative development, where requirements and solutions evolve through collaboration.

TESTING METHODOLOGIES#15

Structured approaches to testing that define how testing is conducted, including strategies like black-box and white-box testing.

COLLABORATIVE DOCUMENTATION#16

A process where multiple team members contribute to and refine documentation to ensure clarity and completeness.

QA TOOLS#17

Software applications designed to assist QA teams in managing and executing testing processes efficiently.

FEEDBACK ANALYSIS#18

The process of evaluating user feedback to identify trends, issues, and opportunities for improvement in a game.

EXECUTIVE SUMMARY#19

A concise overview of a more extensive document or report that highlights key points and findings.

TESTING STRATEGY#20

A high-level approach that outlines how testing will be conducted to meet project goals and requirements.

DEVELOPMENT TEAMS#21

Groups of professionals involved in creating a game, including programmers, artists, and designers, collaborating to achieve quality.

CONTINUOUS INTEGRATION#22

A practice in software engineering where members of a team integrate their work frequently, leading to early detection of issues.

USER INTERFACE (UI) TESTING#23

Testing focused on the graphical and interactive elements of a game to ensure a smooth and intuitive user experience.

FUNCTIONAL TESTING#24

A type of testing that verifies that each function of the software application operates in conformance with the requirement specification.

REGRESSION TESTING#25

Re-testing of a software application to ensure that previously developed and tested features still work after a change.