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






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






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






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






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






6. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






31. Response of the application to an input






32. Testing software in its operational environment






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






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






35. Human action that generates an incorrect result.






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






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






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






39. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






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






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






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






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






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






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






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






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






48. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






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






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