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. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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






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






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






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






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






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






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






9. Integration approach components or subsystems are combined all at once rather than in stages.






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






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






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






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






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






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






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






17. Severity - Priority






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






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






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






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






22. Separation of testing responsibilities which encourages the accomplishment of objective testing






23. A review not based on a formal documented procedure






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






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






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






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






28. Occurrences that happen before and after an unexpected event






29. Waterfall iterative-incremental "V"






30. Response of the application to an input






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






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






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






35. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






38. An analysis that determines the portion of code on software executed by a set of test cases






39. Component - Integration - System - Acceptance






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






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






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






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






44. Human action that generates an incorrect result.






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






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






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






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






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






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