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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






16. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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






18. Actual inputs required to execute a test case






19. Tools used to provide support for and automation of managing various testing documents such as test policy test strategy and test plan






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






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






22. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






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






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






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






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






36. A review not based on a formal documented procedure






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






38. Components or subsystems are integrated and tested one or some at a time until all the components are subsystems are integrated and 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. Measures amount of testing performed by a collection of test cases






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






42. Record details of test cases executed Record order of execution record results






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






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






45. Component - Integration - System - Acceptance






46. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






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






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