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. Tools used to identify and calculate coverage items in program code.






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






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






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






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






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






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






8. Input or combination of inputs required to test software.






9. Component - Integration - System - Acceptance






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






11. Linear Code Sequence and Jump.






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






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






14. Waterfall iterative-incremental "V"






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






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






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






18. Special-purpose software used to simulate a component called by the component under test






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






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






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






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






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






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






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






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






27. Response of the application to an input






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






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






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






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






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






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






34. One defect prevents the detection of another.






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






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






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






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






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






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






41. Severity - Priority






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






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






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






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






46. Conditions required to begin testing activities.






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






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






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






50. Separation of testing responsibilities which encourages the accomplishment of objective testing