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. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






2. Find defects in code while the software application being tested is running.






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






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






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






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






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






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






9. 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).






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






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






12. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






13. Occurrences that happen before and after an unexpected event






14. Waterfall iterative-incremental "V"






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






16. Human action that generates an incorrect result.






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






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






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






20. Testing an integrated system to validate it meets requirements






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






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






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






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






25. A review not based on a formal documented procedure






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






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






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






29. Component - Integration - System - Acceptance






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






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






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






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






34. Conditions required to begin testing activities.






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






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






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






38. Linear Code Sequence and Jump.






39. The capability of a software product to provide agreed and correct output with the required degree of precision






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






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






42. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






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






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






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






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






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






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






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






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