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. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






2. Severity - Priority






3. Testing an integrated system to validate it meets requirements






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






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






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






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






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






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






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






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






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






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






14. A metric used to calculate the number of ALL condition or sub-expression outcomes in code that are executed by a test suite.






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






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






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






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






19. Actual inputs required to execute a test case






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






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






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






23. A document that provides the structure for writing test cases.






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






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






26. Ad hoc method of exposing bugs based on past knowledge and experience of experts (e.g. empty strings illegal characters empty files etc.).






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






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






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






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






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






32. All possible combinations of input values and preconditions are tested.






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






34. The capability of a software product to provide agreed and correct output with the required degree of precision






35. Testing software in its operational environment






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






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






38. Increased load (transations) used to test behavior of system under high volume.






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






40. The process of finding analyzing and removing causes of failure in a software product.






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






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






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






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






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






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






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






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






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






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