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. Input or combination of inputs required to test software.






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






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






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






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






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






7. Testing an integrated system to validate it meets requirements






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






9. Increased load (transations) used to test behavior of system under high volume.






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






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






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






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. Based on analysis of functional specifications of a system.






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






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






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






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






19. Calculates the number of executed branch outcomes in code.






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






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






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






23. Waterfall iterative-incremental "V"






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






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






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






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






28. Assessment of changes required to different layers of documentation and software to implement a given change to the original requirements.






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






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






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






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






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






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






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






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






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






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






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






40. Incident Report - Identifier - Summary - Incident - Description - Impact






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






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






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






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






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






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






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






48. Separation of testing responsibilities which encourages the accomplishment of objective testing






49. One defect prevents the detection of another.






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