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. Allows storage of test input and expected results in one or more central data sources or databases.






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






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






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






5. Calculates the number of executed branch outcomes in code.






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






7. Waterfall iterative-incremental "V"






8. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






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






11. Occurrences that happen before and after an unexpected event






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






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






14. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






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






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






17. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






26. Testing software in its operational environment






27. One defect prevents the detection of another.






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






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






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






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






32. Linear Code Sequence and Jump.






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






34. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






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






36. Component - Integration - System - Acceptance






37. Response of the application to an input






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






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






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






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






42. A review not based on a formal documented procedure






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






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






45. Conditions required to begin testing activities.






46. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






47. Severity - Priority






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






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






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