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. A table showing combinations of inputs and their associated actions.






2. A review not based on a formal documented procedure






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






4. Occurrences that happen before and after an unexpected event






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






6. Testing software in its operational environment






7. Human action that generates an incorrect result.






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






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






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






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






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






13. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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






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






16. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






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






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






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






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






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






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






23. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






25. The process of finding analyzing and removing causes of failure in a software product.






26. Actual inputs required to execute a test case






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






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






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






30. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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