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. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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






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






4. Human action that generates an incorrect result.






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






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






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






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






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






10. Components at lowest level are tested first with higher-level components simulated by drivers. Tested components are then used to test higher-level components. Repeat until all levels have been tested.






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






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






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






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






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






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






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






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






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






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






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






22. Response of the application to an input






23. Conditions required to begin testing activities.






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






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






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






27. Testing software in its operational environment






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






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






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






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






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






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






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






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






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






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






38. Occurrences that happen before and after an unexpected event






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






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






41. Waterfall iterative-incremental "V"






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






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






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






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






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






47. Component - Integration - System - Acceptance






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






49. Severity - Priority






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