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. Component - Integration - System - Acceptance






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






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






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






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






6. Calculates the number of executed branch outcomes in code.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






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






24. Occurrences that happen before and after an unexpected event






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






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






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






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






29. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






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






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






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






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






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






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






44. Conditions required to begin testing activities.






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






46. Human action that generates an incorrect result.






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






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






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






50. Used to test the functionality of software as mentioned in software requirement specifications.