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. Measures amount of testing performed by a collection of test cases






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






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






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






5. An analysis that determines the portion of code on software executed by a set of test cases






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






7. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






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






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






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






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






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






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






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






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






16. Conditions required to begin testing activities.






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






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






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






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






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






22. Conditions ensuring testing process is complete and the object being tested is ready for next stage.






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






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






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






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






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






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






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






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






31. Testing software in its operational environment






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






33. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






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






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






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






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






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






40. A task of maintaining and controlling changes to all entities of a system.






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






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






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






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






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






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






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






48. Component - Integration - System - Acceptance






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






50. Linear Code Sequence and Jump.