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. Sequence in which data items are accessed or modified by code.






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






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






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






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






6. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).






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






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






9. Component - Integration - System - Acceptance






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. Specific groups that represent a set of valid or invalid partitions for input conditions.






12. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






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






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






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






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






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






18. Actual inputs required to execute a test case






19. Testing software components that are separately testable. Also module program and unit testing.






20. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






39. Conditions required to begin testing activities.






40. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






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






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






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






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






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






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






47. Linear Code Sequence and Jump.






48. Human action that generates an incorrect result.






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






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