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. The ratio between the number of defects found and the size of the component/system tested.






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






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






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






5. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






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






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






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






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






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






11. Actual inputs required to execute a test case






12. Testing software in its operational environment






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






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






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






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






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






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






19. Testing an integrated system to validate it meets requirements






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






21. Occurrences that happen before and after an unexpected event






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






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






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






25. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






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






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






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






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






31. Deviation of a software system from its expected delivery services or results






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. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






36. Waterfall iterative-incremental "V"






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






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






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






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






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






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






43. Human action that generates an incorrect result.






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






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






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






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






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






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






50. Conditions required to begin testing activities.