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. Process used to create a SW product from initial conception to public release






2. Occurrences that happen before and after an unexpected event






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






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






5. One defect prevents the detection of another.






6. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






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






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






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






13. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






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






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






17. Find defects in code while the software application being tested is running.






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






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






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






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






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






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






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






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






26. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






38. Linear Code Sequence and Jump.






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






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






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






42. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






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






45. Conditions required to begin testing activities.






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






47. Human action that generates an incorrect result.






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






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






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