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. Used to test the functionality of software as mentioned in software requirement specifications.






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






3. A review not based on a formal documented procedure






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






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






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






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






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






9. Deviation of a software system from its expected delivery services or results






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






11. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






14. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






22. One defect prevents the detection of another.






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






24. Severity - Priority






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






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






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






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






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






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






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






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






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






34. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






36. Testing software in its operational environment






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






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






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






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






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






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






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






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






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






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






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






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






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






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