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 set of one or more test cases. [IEEE 829]

2. Computer programs - procedures - and possibly associated documentation and data pertaining to the operation of a computer system. [IEEE 610]

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

4. Acceptance testing by users/customers at their site - to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes - normally including hardware as well as software.

5. A test environment comprised of stubs and drivers needed to execute a test.

6. Testing to determine how the occurrence of two or more activities within the same interval of time - achieved either by interleaving the activities or by simultaneous execution - is handled by the component or system. [After IEEE 610]

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

8. An element of configuration management - consisting of the evaluation - co-ordination - approval or disapproval - and implementation of changes to configuration items after formal establishment of their configuration identification. [IEEE 610]

9. A type of test tool that enables data to be selected from existing databases or created - generated - manipulated and edited for use in testing.

10. A tool used by programmers to reproduce failures - investigate the state of programs and find the corresponding defect. Debuggers enable programmers to execute programs step by step - to halt a program at any program statement and to set and examine

11. The process of developing and prioritizing test procedures - creating test data and - optionally - preparing test harnesses and writing automated test scripts.

12. A test management task that deals with the activities related to periodically checking the status of a test project. Reports are prepared that compare the actuals to that which was planned. See also test management. The planning - estimating - monito

13. The last executable statement within a component.

14. A black box test design technique in which test cases are designed to execute representatives from equivalence partitions. In principle test cases are designed to cover each partition at least once.

15. A series which appears to be random but is in fact generated according to some prearranged sequence.

16. A capability maturity model structure wherein capability levels provide a recommended order for approaching process improvement within specified process areas. [CMMI]

17. A tool to support performance testing and that usually has two main facilities: load generation and test transaction measurement. Load generation can simulate either multiple users or high volumes of input data. During execution - response time measu

18. A black box test design technique in which test cases are designed to execute combinations of inputs using the concept of condition determination coverage. [TMap]

19. The percentage of branches that have been exercised by a test suite. 100% branch coverage implies both 100% decision coverage and 100% statement coverage.

20. The process of recognizing - investigating - taking action and disposing of defects. It involves recording defects - classifying them and identifying the impact. [After IEEE 1044]

21. A tool that supports the test design activity by generating test inputs from a specification that may be held in a CASE tool repository - e.g. requirements management tool - from specified test conditions held in the tool itself - or from code.

22. Supplied software on any suitable media - which leads the installer through the installation process. It normally runs the installation process - provides feedback on installation results - and prompts for options.

23. The process of testing to determine the compliance of the component or system.

24. A sequence of executable statements within a component.

25. Analysis of software artifacts - e.g. requirements or code - carried out without execution of these software artifacts.

⚡ Recently practiced quizzes in this topic
Live quiz activity
Objective GS (General Studies) in हिन्दी - Indian States & The Company Rajasthan GK Hindi - Fairs & Festivals Objective GS (General Studies) in हिन्दी - Indian Polity - Historical Background of Constitution Objective GS (General Studies) in हिन्दी - Indian Polity - Judiciary Rajasthan GK Hindi - Culture Objective GS in Hindi - General Geography - Air Pressure, Humidity & Air Movement Rajasthan GK Hindi - Energy Rajasthan GK Hindi - Tourism Rajasthan GK Hindi - Rajasthan Introduction Rajasthan GK Hindi - Rivers & Lakes
 
❤ 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 | 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.