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. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






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






3. Human action that generates an incorrect result.






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






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






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






7. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






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






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






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






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






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






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






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






16. Occurrences that happen before and after an unexpected event






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






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






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






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






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






22. Component - Integration - System - Acceptance






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






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






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






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






27. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






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






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






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






34. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






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






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






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






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






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. Events that occurred during the testing process our investigation.






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






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






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






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






45. One defect prevents the detection of another.






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






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






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






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






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