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 called by the component under test






2. Testing an integrated system to validate it meets requirements






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






4. Tools used to identify and calculate coverage items in program code.






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






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






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






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






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






10. Response of the application to an input






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






12. Conditions required to begin testing activities.






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






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






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






16. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






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






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






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






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






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






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






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






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






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






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






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






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






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






31. Operational testing performed at an _external_ site without involvement of the developing organization.






32. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






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






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






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






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






37. A review not based on a formal documented procedure






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






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






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






41. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






42. Severity - Priority






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






44. One defect prevents the detection of another.






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






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






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






48. Human action that generates an incorrect result.






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






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