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. Human action that generates an incorrect result.






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






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






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






6. Response of the application to an input






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






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






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






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






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






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






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






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






15. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






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






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






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






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






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






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






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






23. Testing software in its operational environment






24. Component - Integration - System - Acceptance






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






26. Waterfall iterative-incremental "V"






27. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






28. Severity - Priority






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






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






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






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






33. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






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






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






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






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






47. Occurrences that happen before and after an unexpected event






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






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






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