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. Uses risks to: ID test techniques Determine how much testing is required Prioritize tests with high-priority risks first






2. Conditions required to begin testing activities.






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






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. Black-box testing technique used to create groups of input conditions that create the same kind of output.






6. Occurrences that happen before and after an unexpected event






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






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






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






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






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






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






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






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






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






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






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






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






19. All possible combinations of input values and preconditions are tested.






20. Enables testers to prove that functionality between two or more communicating systems or components is IAW requriements.






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






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






23. Component - Integration - System - Acceptance






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






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






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






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






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






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






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






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






32. Testing performed at development organization's site but outside organization. (I.e. testing is performed by potential customers users or independent testing team)






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






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






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






36. Testing software in its operational environment






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






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






39. A metric to calculate the number of SINGLE condition outcomes that can independently affect the decision outcome.






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






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






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






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






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






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






46. Events that occurred during the testing process our investigation.






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






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






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






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