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. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






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






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






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






5. Severity - Priority






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






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






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






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






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






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






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






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






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






15. Testing software in its operational environment






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






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






18. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






27. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






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






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






32. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






34. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






45. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






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






47. Component - Integration - System - Acceptance






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






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






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