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. Human action that generates an incorrect result.






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






3. A task of maintaining and controlling changes to all entities of a system.






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






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






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






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






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






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






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






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






12. Actual inputs required to execute a test case






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






14. Scheduling Tests Manage test activities Provide interfaces to different tools provide traceability of tests Log test results Prepare progress reports






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






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






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






18. One defect prevents the detection of another.






19. Testing an integrated system to validate it meets requirements






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






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






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






23. Deviation of a software system from its expected delivery services or results






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






25. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






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






37. Increased load (transations) used to test behavior of system under high volume.






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






39. Component - Integration - System - Acceptance






40. Testing software in its operational environment






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






42. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






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






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






47. Severity - Priority






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






49. Occurrences that happen before and after an unexpected event






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