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. Input or combination of inputs required to test software.






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






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






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






5. Linear Code Sequence and Jump.






6. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






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






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






10. One defect prevents the detection of another.






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






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






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






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






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






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






17. Special additions or changes to the environment required to run a test case.






18. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






28. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






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






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






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






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






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






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






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






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






37. Response of the application to an input






38. All possible combinations of input values and preconditions are tested.






39. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






40. Severity - Priority






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






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






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






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






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






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






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






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






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






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