Test your basic knowledge |

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






2. Black-box test design technique - test cases are designed from a decision table.






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






4. Informal testing technique in which test planning and execution run in parallel






5. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






7. Integration approach components or subsystems are combined all at once rather than in stages.






8. Used to replace a component that calls another component.






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






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






11. Sequence in which data items are accessed or modified by code.






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






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






14. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






15. The ratio between the number of defects found and the size of the component/system tested.






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






17. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






19. An event or item that can be tested using one or more test cases






20. One defect prevents the detection of another.






21. Component - Integration - System - Acceptance






22. A document that records the description of each event that occurs during the testing process and that requires further investigation






23. Based on analysis of functional specifications of a system.






24. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






25. A component of the incident report that determines the actual effect of the incident on the software and its users.






26. Events that occurred during the testing process our investigation.






27. Sequence in which instructions are executed through a component or system






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






29. Tools used to store and manage incidents return phone defects failures or anomalies.






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






31. Ability of software to provide appropriate performance relative to amount of resources used.






32. Tools used by developers to identify defects in programs.






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






34. Insertion of additional code in the existing program in order to count coverage items.






35. A functional testing approach in which test cases are designed based on business processes.






36. A set of conditions that a system needs to meet in order to be accepted by end users






37. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






38. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






39. Occurrences that happen before and after an unexpected event






40. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






41. Measures amount of testing performed by a collection of test cases






42. Used to test the functionality of software as mentioned in software requirement specifications.






43. The smallest software item that can be tested in isolation.






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






45. Special additions or changes to the environment required to run a test case.






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






47. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






48. A table showing combinations of inputs and their associated actions.






49. Increased load (transations) used to test behavior of system under high volume.






50. A task of maintaining and controlling changes to all entities of a system.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests