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. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






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






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






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






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






7. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






14. Sequence in which instructions are executed through a component or system






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






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






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






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






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






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






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






22. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






23. Waterfall iterative-incremental "V"






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






25. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






26. Response of the application to an input






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






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






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






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






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






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






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






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






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






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






37. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






38. Based on analysis of functional specifications of a system.






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






40. Conditions required to begin testing activities.






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






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






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






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






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






46. Testing software in its operational environment






47. Human action that generates an incorrect result.






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






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






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