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. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






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






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






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






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






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






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






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






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






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






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






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. All possible combinations of input values and preconditions are tested.






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






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






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






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






20. Behavior or response of a software application that you observe when you execute the action steps in the test case.






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






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






23. Record details of test cases executed Record order of execution record results






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






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






26. A review not based on a formal documented procedure






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






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






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






30. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






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






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






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






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






36. Human action that generates an incorrect result.






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






38. One defect prevents the detection of another.






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






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






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






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






43. Response of the application to an input






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






45. Component - Integration - System - Acceptance






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






47. Actual inputs required to execute a test case






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






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






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