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. Measures amount of testing performed by a collection of test cases






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






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






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






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






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






7. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






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






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






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






11. One defect prevents the detection of another.






12. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






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






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






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






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






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






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






20. Record details of test cases executed Record order of execution record results






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






22. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






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






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






26. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






27. A unique identifier for each incident report generated during test execution.






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






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






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






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






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






33. Incident Report - Identifier - Summary - Incident - Description - Impact






34. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






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






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






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






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






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






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






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






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






45. Component - Integration - System - Acceptance






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






47. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






48. Waterfall iterative-incremental "V"






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






50. Separation of testing responsibilities which encourages the accomplishment of objective testing