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






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






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






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






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






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






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






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






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






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






11. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






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






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






14. Combining components or sytems into larger structural units or subsystems.






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






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






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






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






19. Response of the application to an input






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






21. Human action that generates an incorrect result.






22. Insertion of additional code in the existing program in order to count coverage items.






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






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






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






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






27. Linear Code Sequence and Jump.






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






29. Find defects in code while the software application being tested is running.






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






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






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






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






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






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






36. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






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






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






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






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