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. Integrate different kinds of tools to make test management more efficient and simple.






2. Allows storage of test input and expected results in one or more central data sources or databases.






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






4. A review not based on a formal documented procedure






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






6. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






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






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






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






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






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






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






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






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






16. Severity - Priority






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






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






19. Testing software in its operational environment






20. Linear Code Sequence and Jump.






21. One defect prevents the detection of another.






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






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






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






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






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






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






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






29. Waterfall iterative-incremental "V"






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






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






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






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






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






35. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






38. An analysis that determines the portion of code on software executed by a set of test cases






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






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






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






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






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






44. Human action that generates an incorrect result.






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






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






47. Actual inputs required to execute a test case






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






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






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