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. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






3. Process used to create a SW product from initial conception to public release






4. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






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






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






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






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






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






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






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






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






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






15. One defect prevents the detection of another.






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






17. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






18. Severity - Priority






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






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






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






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






23. Software products or applications designed to automate manual testing tasks.






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






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






26. Allows storage of test input and expected results in one or more central data sources or databases.






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






28. Actual inputs required to execute a test case






29. A review not based on a formal documented procedure






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






31. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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. Special-purpose software used to simulate a component called by the component under test






42. Deviation of a software system from its expected delivery services or results






43. Occurrences that happen before and after an unexpected event






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






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






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






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






48. Human action that generates an incorrect result.






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






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