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. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






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






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






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






5. A review not based on a formal documented procedure






6. Severity - Priority






7. Response of the application to an input






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






9. Conditions required to begin testing activities.






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






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






12. Component - Integration - System - Acceptance






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






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






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






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






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






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






19. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






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






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






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






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






31. One defect prevents the detection of another.






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






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






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






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






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






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






38. Measures amount of testing performed by a collection of test cases






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






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






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






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






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






44. The capability of a software product to provide agreed and correct output with the required degree of precision






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






46. Informal testing technique in which test planning and execution run in parallel






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






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






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






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