ISTQB
Fast practice, instant feedback. Timer auto-submits when time’s up.
Avg score: 49% • Most missed: “A black box test design technique in which test cases are designed from cause-ef…”
ISTQB
Time left 00:00
25 Questions

1. A test basis document that can only be amended by a formal change control process. See also baseline. A specification or software product that has been formally reviewed or agreed upon - that thereafter serves as the basis for further development - a

2. The tracing of requirements through the layers of development documentation to components.

3. The capability of the software product to enable specified modifications to be implemented. [ISO 9126] See also maintainability. The ease with which a software product can be modified to correct defects - modified to meet new requirements - modified

4. 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

5. The process consisting of all life cycle 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

6. A statement of test objectives - and possibly test ideas about how to test. Test charters are used in exploratory testing. See also exploratory testing. An informal test design technique where the tester actively controls the design of the tests as t

7. Any event occurring that requires investigation. [After IEEE 1008]

8. A technique used to characterize the elements of risk. The result of a hazard analysis will drive the methods used for development and testing of a system. See also risk analysis. The process of assessing identified risks to estimate their impact and

9. The process through which decisions are reached and protective measures are implemented for reducing risks to - or maintaining risks within - specified levels.

10. A black box test design technique in which test cases are designed to execute user scenarios.

11. A tree showing equivalence parititions hierarchically ordered - which is used to design test cases in the classification tree method. See also classification tree method. A black box test design technique in which test cases - described by means of a

12. The assessment of change to the layers of development documentation - test documentation and components - in order to implement a given change to specified requirements.

13. Definition of user profiles in performance - load and/or stress testing. Profiles should reflect anticipated or actual usage based on an operational profile of a component or system - and hence the expected workload. See also load profile - operation

14. Multiple heterogeneous - distributed systems that are embedded in networks at multiple levels and in multiple domains interconnected addressing large-scale inter-disciplinary common problems and purposes.

15. Testing of software used to convert data from existing systems for use in replacement systems.

16. A method to determine test suite thoroughness by measuring the extent to which a test suite can discriminate the program from slight variants (mutants) of the program.

17. The consequence/outcome of the execution of a test. It includes outputs to screens - changes to data - reports - and communication messages sent out.

18. A form of state transition testing in which test cases are designed to execute all valid sequences of N+1 transitions. [Chow] See also state transition testing. A black box test design technique in which test cases are designed to execute valid and i

19. The percentage of condition outcomes that have been exercised by a test suite. 100% condition coverage requires each single condition in every decision statement to be tested as True and False.

20. Procedure used to derive and/or select test cases.

21. A systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to prevent their occurrence. See also Failure Mode - Effect and Criticality Analysis (FMECA).

22. A document reporting on any event that occurred - e.g. during the testing - which requires investigation. [After IEEE 829]

23. A minimal software item that can be tested in isolation.

24. A group of test activities aimed at testing a component or system focused on a specific test objective - i.e. functional test - usability test - regression test etc. A test type may take place on one or more test levels or test phases. [After TMap]

25. A high-level description of the test levels to be performed and the testing within those levels for an organization or programme (one or more projects).

⚡ Recently practiced quizzes in this topic
Live quiz activity
Software Testing Tools Inspection And Test Execution ISTQB Glossary of Terms in Software Testing 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 Jasmine.js Practice Test Software Testing Fundamentals Test 2 Software Testing Practice Test Questions
 
❤ If you liked Fatskills, consider supporting us by checking out The Life Manuals You Never Got.

🌈  Our mission is to help improve your scores in any subject and exam withonline quizzes, practice tests, study guides, & advice for students. Since 2018.
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.