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. An analysis that determines the portion of code on software executed by a set of test cases






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






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






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






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






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






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






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






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






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






11. Occurrences that happen before and after an unexpected event






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






13. Component - Integration - System - Acceptance






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






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






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






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






18. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






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






28. One defect prevents the detection of another.






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






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






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






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






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






34. Linear Code Sequence and Jump.






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






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






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






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






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






40. Special-purpose software used to simulate a component called by the component under test






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






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






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






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






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






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






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






48. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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