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. Occurrences that happen before and after an unexpected event






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






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






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






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






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






7. Planning & Control - Analysis and Design - Implementation and Execution - Evaluating Exit - Criteria and Reporting - Closure






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






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






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






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






12. Testing an integrated system to validate it meets requirements






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






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






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






16. Based on the generic iterative-incremental model. Teams work by dividing project tasks into small increments involving only short-term planning to implement various iterations






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






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






19. A review not based on a formal documented procedure






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






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






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






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






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






25. Tests functional or nonfunctional attributes of a system or its components but without referring to the internal structure of the system or its components






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






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






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






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






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






31. Testing performed based on the contract between a customer and the development organization. Customer uses results of the test to determine acceptance of software.






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






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






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






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






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






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






38. Testing performed to detect defects in interfaces and interation between integrated components. Also called "integration testing in the small".






39. Extract data from existing databases to be used during execution of tests make data anonymous generate new records populated with random data sorting records constructing a large number of similar records from a template






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






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






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






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






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






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






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






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






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






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






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