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. Integrate different kinds of tools to make test management more efficient and simple.






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






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






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






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






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






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






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






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






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






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






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






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






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






15. Incident Report - Identifier - Summary - Incident - Description - Impact






16. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






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






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






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






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






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






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






24. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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






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






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






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






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






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






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






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






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






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






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






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






37. Component - Integration - System - Acceptance






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






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






40. Actual inputs required to execute a test case






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






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






43. Testing software in its operational environment






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






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






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






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






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. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






50. Sequence in which instructions are executed through a component or system