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. Deviation of a software system from its expected delivery services or results






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






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






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






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






6. Response of the application to an input






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






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






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






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






11. Input or combination of inputs required to test software.






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






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






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






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






16. Conditions required to begin testing activities.






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






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






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






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






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






22. Testing software in its operational environment






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






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






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






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






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






28. Component - Integration - System - Acceptance






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






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






31. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






41. Used to test the functionality of software as mentioned in software requirement specifications.






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






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






44. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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






46. Human action that generates an incorrect result.






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






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






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






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