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. Waterfall iterative-incremental "V"






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






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






4. Testing software in its operational environment






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






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






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






8. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






19. An event or item that can be tested using one or more test cases






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






21. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






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






23. Commercial Off-The-Shelf products. Products developed for the general market as opposed to those developed for a specific customer.






24. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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. Input or combination of inputs required to test software.






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






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






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






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. A document that provides the structure for writing test cases.






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






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






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






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






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






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






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






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






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






47. Severity - Priority






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






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






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