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. Record details of test cases executed Record order of execution record results






2. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






3. Testing an integrated system to validate it meets requirements






4. Abilitiy of software to collaborate with one or more specified systems subsystem or components.






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






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






7. Human action that generates an incorrect result.






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






9. Actual inputs required to execute a test case






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






11. Testing software in its operational environment






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






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






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






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






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






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






18. Testing performed to determine whether the system meets acceptance criteria






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






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






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






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






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






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






25. The smallest software item that can be tested in isolation.






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






27. Severity - Priority






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






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






30. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






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






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






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






36. Begin with initial requirements specification phase end with implementation and maintenance phases with cyclical transitions in between phases.






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






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






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






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






41. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






50. Conditions required to begin testing activities.