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. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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 table showing combinations of inputs and their associated actions.






4. Testing software in its operational environment






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






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






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






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






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






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






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






12. Integration approach components or subsystems are combined all at once rather than in stages.






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






14. A task of maintaining and controlling changes to all entities of a system.






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






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






17. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






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






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






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






23. Specific groups that represent a set of valid or invalid partitions for input conditions.






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






25. Human action that generates an incorrect result.






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






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






28. Events that occurred during the testing process our investigation.






29. Component - Integration - System - Acceptance






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. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






32. Software products or applications designed to automate manual testing tasks.






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






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






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






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






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






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






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






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






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






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. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






46. Severity - Priority






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






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






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






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