Software testing terms: A select glossary part 1
We recently published an article on a piece of testing jargon: Canary release. Today we expand upon that by looking at select software testing terms in an A-Z format. We love software testing here but even we cannot expect somebody to read through all 26 letters of the alphabet. We are therefore breaking our glossary into multiple parts, with the second set to drop in the weeks ahead.
Software testing glossary – A
Acceptance criteria: This term is used to describe the standards which must be met by a system / component after testing.
Acceptance testing: Once the criteria has been set then this is the type of testing deployed. It typically takes into account elements such as the user requirements and any pertinent business processes.
Accessibility Testing: Another testing type, this is designed to ensure that systems, websites and apps can be used by as many people as possible. It takes into account those people with mental or physical disabilities.
Agile testing: A method of software testing in which testing is incorporated into the development process. The objective is to speed up the time to release by testing at every stage of development.
Alpha testing: Typically completed by internal employees in a stage environment, this is a form of acceptance testing.
Automated testing: The deployment of software tools to test a software product.
Beta-testing: The final round of testing before release is carried out by ‘real’ users in a controlled setting.
Big-bang testing: An approach in which all software components are combined to make a complex system which is then tested as one entity.
Black box testing: Testing is carried out without prior knowledge of a system / software. Testers provide an input and then observe the output to identify how the test subject reacts to expected and unexpected user actions.
Branch testing: A type of white box testing* used to test every possible branch in the control flow graph of a program.
Conversion testing: A type of testing that verifies whether or not a data format can be converted and then used seamlessly by the application under test.
Cyclomatic complexity: This is a measurement used to determine the stability and reliability of a program. There are fewer risks involved in modifying programs with a lower cyclomatic complexity and they are easier to understand
3 letters of the alphabet down, 23 to go – possibly. The first part of our software testing terms series does not include all terminology to fall within the A-C bracket. However, we hope we have selected terms which require a definition. If you disagree then do let us know why!
*We’ll get to W, have no fear!