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






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






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






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






5. A table showing combinations of inputs and their associated actions.






6. Tools used by developers to identify defects in programs.






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






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






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






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






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






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






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






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






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






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






18. Response of the application to an input






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






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






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






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






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






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






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






26. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






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






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






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






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






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






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






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






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






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






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






38. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






40. Linear Code Sequence and Jump.






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






42. Component - Integration - System - Acceptance






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






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






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






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






47. Fixed - Won't Fix - Later - Remind - Duplicate - Incomplete - Not a Bug - Invalid etc.






48. Components are integrated in the order in which they are developed






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






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