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. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






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






4. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






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






7. One defect prevents the detection of another.






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






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






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






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






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






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






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






15. Component - Integration - System - Acceptance






16. Occurrences that happen before and after an unexpected event






17. Components are combined and tested in the order in which basic functionalities start working






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






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






20. Linear Code Sequence and Jump.






21. Combining components or sytems into larger structural units or subsystems.






22. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






23. Allows storage of test input and expected results in one or more central data sources or databases.






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






25. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






26. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






27. Human action that generates an incorrect result.






28. Special-purpose software used to simulate a component called by the component under test






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






30. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






31. Testing an integrated system to validate it meets requirements






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






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






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






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






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






37. Severity - Priority






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






39. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






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






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






42. Testing performed to determine whether the system meets acceptance criteria






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






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






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






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






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






48. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






50. Special-purpose software used to simulate a component that calls the component under test