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 provides the structure for writing test cases.






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






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






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






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






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






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






8. Conditions required to begin testing activities.






9. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






25. A review not based on a formal documented procedure






26. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






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






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






30. Component - Integration - System - Acceptance






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






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






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






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






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






36. Occurrences that happen before and after an unexpected event






37. Severity - Priority






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






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






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






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






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






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






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






45. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






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






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






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