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. Examine changes made to an operational system cause defects.






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






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






4. Conditions required to begin testing activities.






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






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






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






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






9. Response of the application to an input






10. Testing an integrated system to validate it meets requirements






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






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






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






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






15. A review not based on a formal documented procedure






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






17. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






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






21. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






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






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






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






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






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






27. Linear Code Sequence and Jump.






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






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






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






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






32. Black-box techniques used to derive test cases drawing on knowledge intuition and skill of individuals.






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






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






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






36. Severity - Priority






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






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






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






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






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






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






43. One defect prevents the detection of another.






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






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






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






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






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






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






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