ISTQB Glossary of Terms in Software Testing | Practice Test / Quiz / MCQs

Home > Software Testing > Quizzes > ISTQB Glossary of Terms in Software Testing

ISTQB Glossary of Terms in Software Testing

Fast practice, instant feedback. Timer auto-submits when time’s up.

Avg score: 19% • Most missed: “Informal review”

ISTQB (International Software Testing Qualifications Board) is composed of representatives from each existing national board, such as the ASTQB, the American Software Testing Qualifications Board.

Important ISTQB topics are:
1. Testing Techniques: Important testing techniques to focus on are equivalence partitioning and boundary value analysis and related mathematical question.
2. Testing Fundamentals: Important topics to focus on is the STLC, Principles of testing, Early Testing.
3. Testing Tools: Important to learn the 'features' of the various types of testing tools.

ISTQB Glossary of Terms in Software Testing

Time left 00:00

25 Questions

1. Embedded iterative development model

Same as exhaustive testing.Testing of software or a specification by manual simulation of its execution. See also static testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.

2. Resource utilisation

Testing of software or a specification by manual simulation of its execution. See also static testing.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.Same as exhaustive testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.

3. Desk checking

Same as exhaustive testing.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.Testing of software or a specification by manual simulation of its execution. See also static testing.

4. Complete testing

The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.Testing of software or a specification by manual simulation of its execution. See also static testing.Same as exhaustive testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.

5. Integration testing

Testing of software or a specification by manual simulation of its execution. See also static testing.Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. See also component integration testing, system integration testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.

6. Actual result

A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.Testing of software or a specification by manual simulation of its execution. See also static testing.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.The behaviour produced / observed when a component or system is tested under specified conditions.

7. Specification-based technique

Same as black box test design technique.Testing of software or a specification by manual simulation of its execution. See also static testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.

8. Invalid testing

Testing using input values that should be rejected by the component or system. See also error tolerance, negative testing.Testing of software or a specification by manual simulation of its execution. See also static testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.

9. Random testing

Testing of software or a specification by manual simulation of its execution. See also static testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.A black box test design technique where test cases are selected, possibly using a pseudo-random generation algorithm, to match an operational profile.

10. Fishbone diagram

The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.Same as cause/effect diagram .Testing of software or a specification by manual simulation of its execution. See also static testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.

11. Classification tree

A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.Testing of software or a specification by manual simulation of its execution. See also static testing.A tree showing equivalence partitions hierarchically ordered, which is used to design test cases in the classification tree method. See also classification tree method.

12. Outsourced testing

Testing performed by people who are not co-located with the project team and are not fellow employees.Testing of software or a specification by manual simulation of its execution. See also static testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.

13. Incremental testing

Testing where components or systems are integrated and tested one or some at a time until all the components or systems are integrated and tested.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.Testing of software or a specification by manual simulation of its execution. See also static testing.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.

14. Stress testing

A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.Testing of software or a specification by manual simulation of its execution. See also static testing.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified workloads, or with reduced availability of resources such as access to memory or servers. [After IEEE 610] See also performance testing, load testing.

15. Test environment

The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.Testing of software or a specification by manual simulation of its execution. See also static testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.An environment containing hardware, instrumentation, simulators, software tools, and other support elements needed to conduct a test [after IEEE 610].

16. Test data preparation tool

A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.Testing of software or a specification by manual simulation of its execution. See also static testing.A type of test tool that enables data to be selected from existing databases or created, generated, manipulated and edited for use in testing.

17. Mistake

A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.Testing of software or a specification by manual simulation of its execution. See also static testing.Same as error.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.

18. Test estimation

The calculated approximation of a result related to various aspects of testing (e.g. effort spent, completion date, costs involved, number of test cases, etc.) which is usable even if input data may be incomplete, uncertain, or noisy.Testing of software or a specification by manual simulation of its execution. See also static testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.

19. Software integrity level

The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.Testing of software or a specification by manual simulation of its execution. See also static testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.The degree to which software complies or must comply with a set of stakeholder-selected software and/or software-based system characteristics (e.g., software complexity, risk assessment, safety level, security level, desired performance, reliability, or cost) which are defined to reflect the importance of the software to its stakeholders.

20. Baseline

Testing of software or a specification by manual simulation of its execution. See also static testing.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.A specification or software product that has been formally reviewed or agreed upon, that thereafter serves as the basis for further development, and that can be changed only through formal change control process [after IEEE 610].A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.

21. Actual outcome

A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.Same as actual result.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.Testing of software or a specification by manual simulation of its execution. See also static testing.

22. Test case suite

23. LCSAJ testing

Testing of software or a specification by manual simulation of its execution. See also static testing.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.A white box test design technique in which test cases are designed to execute LCSAJs.

24. Basis test set

The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.Testing of software or a specification by manual simulation of its execution. See also static testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.A set of test cases derived from the internal structure of a component or specification to ensure that 100% of a specified coverage criterion will be achieved.

25. SCRUM

Testing of software or a specification by manual simulation of its execution. See also static testing.A development lifecycle sub-model that applies an iterative approach to detailed design, coding and testing within an overall sequential model. In this case, the high level design documents are prepared and approved for the entire project but the actual detailed design, code development and testing are conducted in iterations.An iterative incremental framework for managing projects commonly used with agile software development. See also agile software development.The capability of the software product to use appropriate amounts and types of resources, for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files, when the software performs its function under stated conditions [after ISO 9126]. See also efficiency.

⚡ Recently practiced quizzes in this topic

Live quiz activity

Software Testing Tools Inspection And Test Execution Software Testing MCQs Software Testing Practice Test Automation Testing Knowledge Test Software Testing Practice Test: Software Testing Strategies and Software Matrices Software Testing and Quality Assurance (STQA) Practice Test Questions ISTQB Jasmine.js Practice Test Software Testing Fundamentals Test 2 Software Testing Practice Test Questions

25 Questions

❤ If you liked Fatskills, consider supporting us by checking out The Life Manuals You Never Got.

About | Explore | User Guide | Topics | Subjects | Doubt Solver | Career Aptitude Test | Answers | Free Tools | OSHA Basics Quiz | What Should We Know?
Privacy | Terms |

Without work one finishes nothing. - Ralph Waldo Emerson
© 2026 Fatskills.com

All trademarks, logos and brand names are the property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, trademarks and brands does not imply endorsement.

25 Questions

❤ If you liked Fatskills, consider supporting us by checking out The Life Manuals You Never Got.

About | Explore | User Guide | Topics | Subjects | Doubt Solver | Career Aptitude Test | Answers | Free Tools | OSHA Basics Quiz | What Should We Know? Privacy | Terms |

Without work one finishes nothing. - Ralph Waldo Emerson© 2026 Fatskills.com

All trademarks, logos and brand names are the property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, trademarks and brands does not imply endorsement.

About | Explore | User Guide | Topics | Subjects | Doubt Solver | Career Aptitude Test | Answers | Free Tools | OSHA Basics Quiz | What Should We Know?
Privacy | Terms |

Without work one finishes nothing. - Ralph Waldo Emerson
© 2026 Fatskills.com