Formal testing with respect to user needs, requirements, and business processes conducted to determine whether or not a system satisfies the acceptance criteria and to enable the user, customers or other authorized entity to determine whether or not to accept the system.
The capability of the software product to provide the right or agreed results or effects with the needed degree of precision.
Testing to determine if the game music and sound effects will engage the user in the game and enhance the game play.
A procedure determining whether a person or a process is, in fact, who or what it is declared to be.
The response of a component or system to a set of input values and preconditions.
A logical expression that can be evaluated as True or False.
The process of confirming that a component, system or person complies with its specified requirements.
Testing based on an analysis of the internal structure of the component or system.
Testing based on an analysis of the internal structure of the component or system.
The degree to which a component or system can exchange information with other components or systems, and/or perform its required functions while sharing the same hardware or software environment.
The capability of the software product to adhere to standards, conventions or regulations in laws and similar prescriptions.
Testing to determine the compliance of the component or system.
A logical expression that can be evaluated as True or False.
The composition of a component or system as defined by the number, nature, and interconnections of its constituent parts.
Testing to determine the portability of a software product.
Testing to determine the compliance of the component or system.
A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system.
A type of testing in which business processes are tested from start to finish under production-like circumstances.
A type of testing in which business processes are tested from start to finish under production-like circumstances.
A human action that produces an incorrect result.
A test is deemed to fail if its actual result does not match its expected result.
The status of a test result in which the actual result does not match the expected result.
The backup operational mode in which the functions of a system that becomes unavailable are assumed by a secondary system.
Testing by simulating failure modes or actually causing failures in a controlled environment. Following a failure, the failover mechanism is tested to ensure that data is not lost or corrupted and that any agreed service levels are maintained (e.g., function availability or response times).
The process of intentionally adding defects to a system for the purpose of finding out whether the system can detect, and possibly recover from, a defect. Fault injection is intended to mimic failures that might occur in the field.
A distinguishing characteristic of a component or system.
Testing based on an analysis of the internal structure of the component or system.
An organization responsible to test and certify that the software, hardware, firmware, platform, and operating system follow all the jurisdictional rules for each location where the product will be used.
The process of combining components or systems into larger assemblies.
A type of integration testing performed to determine whether components or systems pass data and control correctly to one another.
Testing to determine the interoperability of a software product.
The activities performed at each stage in software development, and how they relate to one another logically and chronologically.
Testing based on an analysis of the internal structure of the component or system.
Testing based on an analysis of the internal structure of the component or system.
Testing to determine the correctness of the pay table implementation, the random number generator results, and the return to player computations.
The number or category assigned to an attribute of an entity by making a measurement.
A memory access failure due to a defect in a program's dynamic store allocation logic that causes it to fail to release memory after it has finished using it, eventually causing the program and/or other concurrent processes to fail due to lack of memory.
A measurement scale and the method used for measurement.
A human action that produces an incorrect result.
Testing to determine if many players can simultaneously interact with the casino game world, with computer-controlled opponents, game servers, and with each other, as expected according to the game design.
The consequence/outcome of the execution of a test.
Testing to determine that the game returns the correct mathematical results to the screen, to the players' accounts, and to the casino account.
A test is deemed to pass if its actual result matches its expected result.
The status of a test result in which the actual result matches the expected result.
A testing technique aiming to exploit security vulnerabilities (known or unknown) to gain unauthorized access.
Testing to determine the performance of a software product.
Testing done by testers from a player's perspective to validate player satisfaction.
Testing to determine the portability of a software product.
A set of interrelated activities, which transform inputs into outputs.
A set of conventions that govern the interaction of processes, devices, and other components within a system.
A series which appears to be random but is in fact generated according to some prearranged sequence.
The degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations.
Part of quality management focused on providing confidence that quality requirements will be fulfilled.
Testing to determine the compliance of the component or system.
Testing to determine the reliability of a software product.
The consequence/outcome of the execution of a test.
Testing to determine the scalability of the software product.
Testing to determine the security of the software product.
A type of development lifecycle model in which a complete system is developed in a linear way of several discrete and successive phases with no overlap between them.
The representation of selected behavioral characteristics of one physical or abstract system by another system.
A device, computer program or system used during testing, which behaves or operates like a given system when provided with a set of controlled inputs.
Computer programs, procedures, and possibly associated documentation and data pertaining to the operation of a computer system.
The activities performed at each stage in software development, and how they relate to one another logically and chronologically.
A distinguishing characteristic of a component or system.
Documentation that provides a detailed description of a component or system for the purpose of developing and testing it.
Formal, possibly mandatory, set of requirements developed and used to prescribe consistent approaches to the way of working or to provide guidelines (e.g., ISO/IEC standards, IEEE standards, and organizational standards).
Testing to determine the compliance of the component or system.
Testing based on an analysis of the internal structure of the component or system.
Testing based on an analysis of the internal structure of the component or system.
Testing an integrated system to verify that it meets specified requirements.
A set of one or more test cases.
The use of software to perform or support test activities, e.g., test management, test design, test execution and results checking.
An instance of the test process against a single identifiable version of the test object.
A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system.
The consequence/outcome of the execution of a test.
The activity of establishing or updating a test plan.
The consequence/outcome of the execution of a test.
A procedure used to derive and/or select test cases.
A skilled professional who is involved in the testing of a component or system.
The process consisting of all lifecycle activities, both static and dynamic, concerned with planning, preparation and evaluation of software products and related work products to determine that they satisfy specified requirements, to demonstrate that they are fit for purpose and to detect defects.
All components of a system that provide information and controls for the user to accomplish specific tasks with the system.
Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled.
Testing based on an analysis of the internal structure of the component or system.