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. Scripting technique that uses data files to store test input expected results and keywords related to a software application being tested.






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






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






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






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






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






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






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






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






10. Testing an integrated system to validate it meets requirements






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






12. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






14. Component - Integration - System - Acceptance






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






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






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






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






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






20. Waterfall iterative-incremental "V"






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






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






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






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






25. Severity - Priority






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






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






28. Actual inputs required to execute a test case






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






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






31. One defect prevents the detection of another.






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






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






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






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






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






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






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






39. Testing software in its operational environment






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






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






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






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. Calculates the number of executed branch outcomes in code.






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






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






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






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






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






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