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 document that records the description of each event that occurs during the testing process and that requires further investigation






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






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






4. Component - Integration - System - Acceptance






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






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






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






8. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






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






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






11. A review not based on a formal documented procedure






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






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






14. A component of the incident report that determines the actual effect of the incident on the software and its users.






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






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






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






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






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






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






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






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






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






24. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






42. Behavior or response of a software application that you observe when you execute the action steps in the test case.






43. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






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






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






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






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