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. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






3. Response of the application to an input






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






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






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






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






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






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






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






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






12. Conditions required to begin testing activities.






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






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






15. Testing software in its operational environment






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






17. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






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






21. Component - Integration - System - Acceptance






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






23. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






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






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






26. Occurrences that happen before and after an unexpected event






27. Waterfall iterative-incremental "V"






28. Special additions or changes to the environment required to run a test case.






29. A functional testing approach in which test cases are designed based on business processes.






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






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






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






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






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






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






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






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






38. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






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






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






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






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






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






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






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






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






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






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