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 task of maintaining and controlling changes to all entities of a system.






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






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






4. Waterfall iterative-incremental "V"






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






6. Conditions required to begin testing activities.






7. Severity - Priority






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






28. Informal testing technique in which test planning and execution run in parallel






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






30. A review not based on a formal documented procedure






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






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






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






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






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






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






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






38. Specific groups that represent a set of valid or invalid partitions for input conditions.






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






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






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






42. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






44. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






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






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






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






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






49. Tools used to keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).






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