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 table showing combinations of inputs and their associated actions.






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






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






4. Occurrences that happen before and after an unexpected event






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






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






7. A document that provides the structure for writing test cases.






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






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






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






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






12. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






20. Response of the application to an input






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






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






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






24. Increased load (transations) used to test behavior of system under high volume.






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






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






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






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






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






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






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






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






33. Used to test the functionality of software as mentioned in software requirement specifications.






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






35. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






43. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






44. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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






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






48. Testing an integrated system to validate it meets requirements






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






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