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 keep track of different versions variants and releases of software and test artifacts (such as design documents test plans and test cases).






2. Response of the application to an input






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






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






5. Component - Integration - System - Acceptance






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






7. Examine changes made to an operational system cause defects.






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






9. One defect prevents the detection of another.






10. A set of conditions that a system needs to meet in order to be accepted by end users






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






12. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






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






14. Linear Code Sequence and Jump.






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






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






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






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






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






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






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






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






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






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






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






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






27. A black-box test design technique used to identify possible causes of a problem by using the cause-effect diagram






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






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






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






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






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






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






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






35. Testing an integrated system to validate it meets requirements






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






37. Actual inputs required to execute a test case






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






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






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






41. Conditions required to begin testing activities.






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






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






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






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






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






47. Occurrences that happen before and after an unexpected event






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






49. Human action that generates an incorrect result.






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