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. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






3. One defect prevents the detection of another.






4. Insertion of additional code in the existing program in order to count coverage items.






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






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. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






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






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






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






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






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






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






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






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






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. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






23. Components are integrated in the order in which they are developed






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






25. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






26. Waterfall iterative-incremental "V"






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






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






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






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






31. Severity - Priority






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






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






34. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






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






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






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






46. Sequence in which data items are accessed or modified by code.






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






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






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






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