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. Allows storage of test input and expected results in one or more central data sources or databases.






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






3. Component - Integration - System - Acceptance






4. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






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






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






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






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






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






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






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






15. One defect prevents the detection of another.






16. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






17. Conditions required to begin testing activities.






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






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






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






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






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






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






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






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






26. Testing software components that are separately testable. Also module program and unit testing.






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






28. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






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






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






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






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






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






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






35. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






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






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






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






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






49. Special additions or changes to the environment required to run a test case.






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