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. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






7. Actual inputs required to execute a test case






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






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






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






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






12. One defect prevents the detection of another.






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






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






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






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






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






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






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






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






21. Nonfunctional testing including testing: ease of fixing defects - ease of meeting new requirements - ease of maintenance






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






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






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






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






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. The capability of a software product to provide functions that address explicit and implicit requirements from the product against specified conditions.






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






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






30. Component - Integration - System - Acceptance






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






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






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






34. Response of the application to an input






35. Linear Code Sequence and Jump.






36. Black-box test design technique - test cases are designed from a decision table.






37. A review not based on a formal documented procedure






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






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






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






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






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






43. Occurrences that happen before and after an unexpected event






44. Based on analysis of functional specifications of a system.






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






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






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






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






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






50. Ease with which software cna be modified to correct defects meet new requirements make future maintenance easier or adapt to a changed environment.