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. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






2. Specific groups that represent a set of valid or invalid partitions for input conditions.






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






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






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






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. A unique identifier for each incident report generated during test execution.






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






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






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






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






12. Human action that generates an incorrect result.






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






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






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






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. Sequence in which instructions are executed through a component or system






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






19. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






21. Severity - Priority






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






23. Inputs - Expected Results - Actual Results - Anomalies - Date & Time - Procedure Step - Attempts to repeat - Testers - Observers






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






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






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






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






28. A review not based on a formal documented procedure






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






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






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






32. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






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






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






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






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






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






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






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






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






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






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






44. Testing software in its operational environment






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






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






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






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






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






50. Testing an integrated system to validate it meets requirements