SOFTWARE TESTING GLOSSARY – THICHBLOG.NET

SOFTWARE TESTING GLOSSARY

A
API Testing
API testing is a type of software testing where application programming interfaces (APIs) are tested to determine if they meet expectations for functionality, reliability, performance, and security.

(Another definition from ISTQB: Testing performed by submitting requests to the test object using its application programming interface.)
Alpha testing
A type of acceptance testing performed in the developer’s test environment by roles outside the development organization. (ISTQB)
B
Beta testing
A type of acceptance testing performed at an external site to the developer’s test environment by roles outside the development organization. (ISTQB)
F
Flaky Test
A test is considered to be flaky when it can pass and fail across multiple retry attempts without any code changes.
For example, a test is executed and fails, then the test is executed again, without any change to the code, but this time it passes.
G
Gorilla Testing
Gorilla Testing is a Software testing technique wherein a module of the program is repeatedly tested to ensure that it is working correctly and there is no bug in that module. A module can be tested over a hundred times, and in the same manner. So, Gorilla Testing is also known as “Frustrating Testing”.
L
Latent Bug
Latent Bug is an uncovered or unidentified bug which exists in the system over a period of time is known as the Latent Bug. The bug may persist in the system in one or more versions of the software.
M
Middleware
Middleware is computer software that provides services to software applications beyond those available from the operating system. It can be described as “software glue”.[1]
Middleware makes it easier for software developers to implement communication and input/output, so they can focus on the specific purpose of their application.
Monkey Testing
Monkey testing is a type of software testing in which a software or application is tested using random inputs with the sole purpose of trying and breaking the system. There are no rules in this type of testing. It completely works on the tester’s mood or gut feeling and experience.
P
Persona
A fictional character representing a certain type of users and how they will interact with the system.
S
SLA
A service-level agreement (SLA) is defined as an official commitment that prevails between a service provider and the customer.
Story Mapping
A technique ordering user stories on two dimensions, the horizontal axis representing their execution order, and the vertical axis representing the sophistication of the implemented product.
Storyboard

A visual representation of the system in which user stories are represented in context for the purpose of understanding the business processes.
T
Test Basic
Test Basic is a document or source of information that is needed to write test cases and perform test analysis.
Test Oracles
A source to determine expected results to compare with the actual result of the software under test. An oracle may be the existing system (for a benchmark), other software, a user manual, or an individual’s specialized knowledge, but should not be the code.
Test strategy
A test strategy is an outline that describes the testing approach of the software development cycle. The purpose of a test strategy is to provide a rational deduction from organizational, high-level objectives to actual test activities to meet those objectives from a quality assurance perspective.