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. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






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






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






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






7. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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 provide support for and automation of managing various testing documents such as test policy test strategy and test plan






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






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






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






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






14. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






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






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






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






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






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






20. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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






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






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






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






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






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






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






28. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






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






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






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






42. Used to test the functionality of software as mentioned in software requirement specifications.






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






44. Component - Integration - System - Acceptance






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






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






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






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






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






50. Testing an integrated system to validate it meets requirements