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. Special-purpose software used to simulate a component called by the component under test






2. Metric used to calculate the number of combinations of all single condition outcomes within one statement that are executed by a test case.






3. Tracing requirements for a level of testing using test documentation from the test plan to the test script.






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






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






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






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






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






9. Integration approach components or subsystems are combined all at once rather than in stages.






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






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






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






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






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






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






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






17. A review not based on a formal documented procedure






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






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






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






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






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






23. Testing an integrated system to validate it meets requirements






24. Component - Integration - System - Acceptance






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






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






27. Input or combination of inputs required to test software.






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






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






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






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






32. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






33. Occurrences that happen before and after an unexpected event






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






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






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






37. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






47. One defect prevents the detection of another.






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






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






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