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. Allows storage of test input and expected results in one or more central data sources or databases.






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






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






5. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






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






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






18. Conditions required to begin testing activities.






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






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






21. A set of conditions that a system needs to meet in order to be accepted by end users






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






23. Bug fault internal error problem etc. Flaw in software that causes it to fail to perform its required functions.






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






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






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






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






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






29. Frequency of tests failing per unit of measure (e.g. time number of transactions test cases executed.)






30. Severity - Priority






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






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






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






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






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






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






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






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






39. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






40. Response of the application to an input






41. Actual inputs required to execute a test case






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






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






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






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






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






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






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






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






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