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. A test case design technique for a software component to ensure that the outcome of a decision point or branch in cod is tested.






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






3. Occurrences that happen before and after an unexpected event






4. Testing software in its operational environment






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






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






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






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






9. Response of the application to an input






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






11. Deviation of a software system from its expected delivery services or results






12. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






13. Component - Integration - System - Acceptance






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






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






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






17. Conditions required to begin testing activities.






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






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






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






21. One defect prevents the detection of another.






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






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






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






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






26. A task of maintaining and controlling changes to all entities of a system.






27. Linear Code Sequence and Jump.






28. Human action that generates an incorrect result.






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






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






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






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






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






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






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






36. Incremental rollout Adapt processes testware etc. to fit with use of tool Adequate training Define guidelines for use of tool (from pilot project) Implement continuous improvement mechanism Monitor use of tool Implement ways to learn lessons






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






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






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






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






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






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






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






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






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






46. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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