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. Component - Integration - System - Acceptance






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






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






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






5. An analysis that determines the portion of code on software executed by a set of test cases






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






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






8. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






9. Integrate different kinds of tools to make test management more efficient and simple.






10. Human action that generates an incorrect result.






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






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






13. Response of the application to an input






14. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






15. Calculates the number of executed branch outcomes in code.






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






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






18. A document that provides the structure for writing test cases.






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






20. Black-box testing technique used to create groups of input conditions that create the same kind of output.






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






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






23. Linear Code Sequence and Jump.






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






25. Conditions required to begin testing activities.






26. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






28. Testing software in its operational environment






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






30. Components are integrated in the order in which they are developed






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






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






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






34. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






36. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






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






38. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






40. Examine changes made to an operational system cause defects.






41. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






42. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






43. Operational testing performed at an _external_ site without involvement of the developing organization.






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






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






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






47. The capability of a software product to provide agreed and correct output with the required degree of precision






48. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






49. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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