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. Test case design technique used to identify bugs occurring on or around boundaries of equivalence partitions.






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






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






4. Check to make sure a system adheres to a defined set of standards conventions or regulations in laws and similar specifications.






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






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






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






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






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






10. Actual inputs required to execute a test case






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






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






13. Special-purpose software used to simulate a component that calls the component under test






14. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






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






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






17. Review documents (reqs architecture design etc.) ID conditions to be tested Design tests Assess testability of reqs ID infrastructure & tools






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






19. Components are combined and tested in the order in which basic functionalities start working






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






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






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






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






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






25. Tools used to store and manage incidents return phone defects failures or anomalies.






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






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






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






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






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






31. Occurrences that happen before and after an unexpected event






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






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






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






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






36. Conditions required to begin testing activities.






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






38. A review not based on a formal documented procedure






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






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






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






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






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






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






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






46. Linear Code Sequence and Jump.






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






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






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






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