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. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






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






3. Waterfall iterative-incremental "V"






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






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






6. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






16. A review not based on a formal documented procedure






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






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






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






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






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






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






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






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






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






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






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






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






29. Tools used to store and manage incidents return phone defects failures or anomalies.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






44. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






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






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






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. The ratio between the number of defects found and the size of the component/system tested.






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






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