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. Find defects in code while the software application being tested is running.






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






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






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






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






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






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






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






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






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






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






12. Human action that generates an incorrect result.






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






14. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






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






16. Calculates the number of executed branch outcomes in code.






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






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






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






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






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






22. Events that occurred during the testing process our investigation.






23. A review not based on a formal documented procedure






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






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






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






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






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






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






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






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






32. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






35. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






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






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






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






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






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






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






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






43. Separation of testing responsibilities which encourages the accomplishment of objective testing






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






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






46. Linear Code Sequence and Jump.






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






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






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






50. Component - Integration - System - Acceptance