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. Events that occurred during the testing process our investigation.






2. Component - Integration - System - Acceptance






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






4. Response of the application to an input






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






6. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






7. Process used to create a SW product from initial conception to public release






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






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






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






11. Tool or hardware device that runs in parallel to assembled component. It manages records and analyzes the behavior of the tested system.






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






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






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






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






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






17. A review not based on a formal documented procedure






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






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






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






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






22. Conditions required to begin testing activities.






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






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






25. Integration Approach: A frame or backbone is created and components are progressively integrated into it.






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






27. Not related to the actual functionality e.g. reliability efficiency usability maintainability portability etc.






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






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






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






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






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






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






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






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






36. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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






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






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






48. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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