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. Measure & analyze results of testing; Monitor document share results of testing; Report information on testing; Initiate actions to improve processes; Make decisions about testing






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






3. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






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






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






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






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






8. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






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






20. Waterfall iterative-incremental "V"






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






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






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






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






25. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






26. One defect prevents the detection of another.






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






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






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






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






31. A unique identifier for each incident report generated during test execution.






32. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






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






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






37. Component - Integration - System - Acceptance






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






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






40. Software products or applications designed to automate manual testing tasks.






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






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






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






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






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






46. Human action that generates an incorrect result.






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






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






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






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