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. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






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






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






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






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






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






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






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






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






14. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






22. Severity - Priority






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






24. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






25. Conditions required to begin testing activities.






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






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






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






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






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






31. Response of the application to an input






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






33. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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






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






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






37. Black-box test design technique - test cases are designed from a decision table.






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






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






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






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






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






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






44. Integration approach components or subsystems are combined all at once rather than in stages.






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






46. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






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






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






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