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






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






3. Human action that generates an incorrect result.






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






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






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






7. Operational testing performed at an _external_ site without involvement of the developing organization.






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






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






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






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






12. Informal testing technique in which test planning and execution run in parallel






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






14. Simple & easy to follow Its rigidity makes it easy to follow It's typically well planned - Systematic - Freezing requirements before development begins ensures no rework later Each phase has specific deliverables






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






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






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






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






19. ID SW products - components - risks - objectives; Estimate effort; Consider approach; Ensure adherence to organization policies; Determine team structure; Set up test environment; Schedule testing tasks & activities






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






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






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






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






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






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






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






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






28. Waterfall iterative-incremental "V"






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






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






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






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






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






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






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






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






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






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






39. A code metric that specifies the number of independent paths through a program. Enables identification of complex (and therefore high-risk) areas of code.






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






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






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






43. Occurrences that happen before and after an unexpected event






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






45. Integration approach components or subsystems are combined all at once rather than in stages.






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






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






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






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






50. A review not based on a formal documented procedure