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. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






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






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






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






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






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






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






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






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






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






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






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






15. Testing performed to determine whether the system meets acceptance criteria






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






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






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






19. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






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






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






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






23. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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






25. Waterfall iterative-incremental "V"






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






27. Human action that generates an incorrect result.






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






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






30. The smallest software item that can be tested in isolation.






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






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






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






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






35. Severity - Priority






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






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






38. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






39. Sequence in which instructions are executed through a component or system






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






41. Allows storage of test input and expected results in one or more central data sources or databases.






42. A technique used to improve testing coverage by deliberately introducing faults in code.






43. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






Can you answer 50 questions in 15 minutes?



Let me suggest you:



Major Subjects



Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Most popular tests