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 identify and calculate coverage items in program code.






2. Occurrences that happen before and after an unexpected event






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






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






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






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






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






8. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






17. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






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






20. Special-purpose software used to simulate a component that calls the component under test






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






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






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






24. Human action that generates an incorrect result.






25. Conditions required to begin testing activities.






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






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






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






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






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






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






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






33. A unique identifier for each incident report generated during test execution.






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






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






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






37. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






38. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






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






40. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






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