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. Response of the application to an input






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






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






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






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






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






7. One defect prevents the detection of another.






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






9. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






12. Actual inputs required to execute a test case






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






14. A functional testing approach in which test cases are designed based on business processes.






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






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






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






18. Testing an integrated system to validate it meets requirements






19. A review not based on a formal documented procedure






20. Severity - Priority






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






22. Requirements Analysis - Design - Coding - Integration - Implementation - Maintenance






23. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






24. Conditions required to begin testing activities.






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






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






27. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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