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. Execute individual & groups of test cases Record results Compare results with expected Report differenes between actual & expected Re-execute to verify fixes






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






3. Combining components or sytems into larger structural units or subsystems.






4. A review not based on a formal documented procedure






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






6. Response of the application to an input






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






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






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






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






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






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






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






14. Actual inputs required to execute a test case






15. Testing an integrated system to validate it meets requirements






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






17. Ability of software to provide appropriate performance relative to amount of resources used.






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






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






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






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






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






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






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






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






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






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






28. Waterfall iterative-incremental "V"






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






30. One defect prevents the detection of another.






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






32. A technique used to improve testing coverage by deliberately introducing faults in code.






33. Human action that generates an incorrect result.






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






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






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






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






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






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






40. Unconfirmed - New - Open - Assigned - Resolved - Verified - Closed






41. A type of review that involves visual examination of documents to detect defects such as violations of development standards and non-conformance to higher-level documentation.






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






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






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






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






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






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






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






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






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