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. Ability of software to provide appropriate performance relative to amount of resources used.






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






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






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






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






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






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






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






9. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






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






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






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






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






15. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






18. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






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






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






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






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






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






27. Human action that generates an incorrect result.






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






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






30. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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






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






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






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






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






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






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






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






39. Testing an integrated system to validate it meets requirements






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






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






42. 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).






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






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






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






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






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






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






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






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