CTFL
Fast practice, instant feedback. Timer auto-submits when time’s up.
Avg score: 40% • Most missed: “Used to replace a component that calls another component.”
CTFL
Time left 00:00
25 Questions

1. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.

2. The process of finding analyzing and removing causes of failure in a software product.

3. Specific groups that represent a set of valid or invalid partitions for input conditions.

4. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure

5. Find defects in code while the software application being tested is running.

6. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.

7. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)

8. Requirements that determine the functionality of a software system.

9. All possible combinations of input values and preconditions are tested.

10. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.

11. Occurrences that happen before and after an unexpected event

12. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first

13. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.

14. Testing software components that are separately testable. Also module program and unit testing.

15. Process used to create a SW product from initial conception to public release

16. Tests interfaces between components and between integrated components and systems.

17. Abilitiy of software to collaborate with one or more specified systems subsystem or components.

18. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.

19. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.

20. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and tested.

21. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.

22. Software products or applications designed to automate manual testing tasks.

23. Tools used to identify and calculate coverage items in program code.

24. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).

25. Actual inputs required to execute a test case

⚡ 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 ISTQB Jasmine.js Practice Test Software Testing Fundamentals Test 2
 
❤ 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.