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. Used to test the functionality of software as mentioned in software requirement specifications.






2. The process of finding analyzing and removing causes of failure in a software product.






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






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






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






6. Testing an integrated system to validate it meets requirements






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






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






9. Response of the application to an input






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






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






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






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






14. Conditions required to begin testing activities.






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






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






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






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






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






20. Waterfall iterative-incremental "V"






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






22. Human action that generates an incorrect result.






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






24. White-box design technique used to design test cases for a software component using LCSAJ.






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






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






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






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






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






30. Testing software components that are separately testable. Also module program and unit testing.






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






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






33. Component - Integration - System - Acceptance






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






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






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






37. Actual inputs required to execute a test case






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






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






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






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






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






43. Linear Code Sequence and Jump.






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






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






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






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






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






49. Tools used to identify and calculate coverage items in program code.






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