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. Component - Integration - System - Acceptance






2. Based on analysis of functional specifications of a system.






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






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






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






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






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






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






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






10. Testing software in its operational environment






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






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






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






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






15. The capability of a software product to provide agreed and correct output with the required degree of precision






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






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






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






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






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






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






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






23. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






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






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






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






37. Testing an integrated system to validate it meets requirements






38. Severity - Priority






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






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






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






42. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






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






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






48. A review not based on a formal documented procedure






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






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