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. A document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






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






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






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






7. Testing software in its operational environment






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






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






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






11. All possible combinations of input values and preconditions are tested.






12. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






13. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






46. Conditions required to begin testing activities.






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






48. One defect prevents the detection of another.






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






50. Linear Code Sequence and Jump.