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. Actual inputs required to execute a test case






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






3. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






10. Waterfall iterative-incremental "V"






11. Response of the application to an input






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






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






14. Human action that generates an incorrect result.






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






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






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






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






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






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






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






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






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






24. Severity - Priority






25. Develop & proiroitize test cases Create groups of test cases Set up test environment






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






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






28. One defect prevents the detection of another.






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






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






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






32. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






39. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






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






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






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






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






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






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






47. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.






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






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






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