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. Acceptance testing by users/customers at their site - to determine whether or not a component or system satisfies the user/customer needs and fits within the business processes - normally including hardware as well as software.






2. A scripting technique that stores test input and expected results in a table or spreadsheet - so that a single control script can execute all of the tests in the table. Data driven testing is often used to support the application of test execution to






3. A test is deemed to fail if its actual result does not match its expected result.






4. The percentage of executable statements that have been exercised by a test suite.






5. A tool that carries out static analysis.






6. A step-by-step presentation by the author of a document in order to gather information and to establish a common understanding of its content. [Freedman and Weinberg - IEEE 1028] See also peer review. A review of a software work product by colleagues






7. A framework that describes the key elements of an effective product development and maintenance process. The Capability Maturity Model Integration covers best-practices for planning - engineering and managing product development and maintenance. CMMI






8. The insertion of additional code into the program in order to collect information about program behavior during execution - e.g. for measuring code coverage.






9. The totality of functionality and features of a software product that bear on its ability to satisfy stated or implied needs. [After ISO 9126]






10. A system whose failure or malfunction may result in death or serious injury to people - or loss or severe damage to equipment - or environmental harm.






11. A set of interrelated activities - which transform inputs into outputs. [ISO 12207]






12. A tool that facilitates the recording and status tracking of defects and changes. They often have workflow-oriented facilities to track and control the allocation - correction and re-testing of defects and provide reporting facilities. See also incid






13. The response of a component or system to a set of input values and preconditions.






14. Attributes of software products that bear on its ability to prevent unauthorized access - whether accidental or deliberate - to programs and data. [ISO 9126] See also functionality. The capability of the software product to provide functions which me






15. A distinct set of test activities collected into a manageable phase of a project - e.g. the execution activities of a test level. [After Gerrard]






16. Testing by means of a random selection from a large range of inputs and by randomly pushing buttons - ignorant on how the product is being used.






17. The number of defects identified in a component or system divided by the size of the component or system (expressed in standard measurement terms - e.g. lines-of-code - number of classes or function points).






18. The tracing of requirements through the layers of development documentation to components.






19. Testing performed to expose defects in the interfaces and in the interactions between integrated components or systems. See also component integration testing - system integration testing. Testing performed to expose defects in the interfaces and int






20. The process of confirming that a component - system or person complies with its specified requirements - e.g. by passing an exam.






21. The set of generic and specific conditions for permitting a process to go forward with a defined task - e.g. test phase. The purpose of entry criteria is to prevent a task from starting which would entail more (wasted) effort compared to the effort n






22. A group of test activities aimed at testing a component or system focused on a specific test objective - i.e. functional test - usability test - regression test etc. A test type may take place on one or more test levels or test phases. [After TMap]






23. A tool used to check that no brtoken hyperlinks are present on a web site.






24. Procedure to derive and/or select test cases based on the tester's experience - knowledge and intuition.






25. An attribute of a component or system specified or implied by requirements documentation (for example reliability - usability or design constraints). [After IEEE 1008]






26. A path that cannot be exercised by any set of possible input values.






27. An analysis technique aimed at identifying the root causes of defects. By directing corrective measures at root causes - it is hoped that the likelihood of defect recurrence will be minimized.






28. The capability of the software product to adhere to standards - conventions or regulations in laws and similar prescriptions. [ISO 9126]






29. A program element is said to be exercised by a test case when the input value causes the execution of that element - such as a statement - decision - or other structural element.






30. Testing of a previously tested program following modification to ensure that defects have not been introduced or uncovered in unchanged areas of the software - as a result of the changes made. It is performed when the software or its environment is c






31. The first executable statement within a component.






32. A questionnaire based usability test technique to evaluate the usability - e.g. user-satisfaction - of a component or system. [Veenendaal]






33. A test tool to perform automated test comparison of actual results with expected results.






34. A black box test design technique in which test cases are designed to execute user scenarios.






35. A document reporting on any flaw in a component or system that can cause the component or system to fail to perform its required function. [After IEEE 829]






36. Any (work) product that must be delivered to someone other than the (work) product's author.






37. A tool for seeding (i.e. intentionally inserting) faults in a component or system.






38. An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either side of an edge - for example the minimum or maximum value of a range.






39. A specification or software product that has been formally reviewed or agreed upon - that thereafter serves as the basis for further development - and that can be changed only through a formal change control process. [After IEEE 610]






40. The degree of impact that a defect has on the development or operation of a component or system. [After IEEE 610]






41. The capability of the software product to co-exist with other independent software in a common environment sharing common resources. [ISO 9126] See also portability. The ease with which the software product can be transferred from one hardware or sof






42. The process of testing to determine the compliance of the component or system.






43. Testing where the system is subjected to large volumes of data. See also resource-utilization testing. The process of testing to determine the resource-utilization of a software product.






44. A device or storage area used to store data temporarily for differences in rates of data flow - time or occurrence of events - or amounts of data that can be handeld by the devices or processes involved in the transfer or use of the data. [IEEE 610]






45. A systematic way of testing all-pair combinations of variables using orthogonal arrays. It significantly reduces the number of all combinations of variables to test all pair combinations. See also pairwise testing. A black box test design technique i






46. The organizational artifacts needed to perform testing - consisting of test environments - test tools - office environment and procedures.






47. The process of combining components or systems into larger assemblies.






48. A tool that provides support for testing security characteristics and vulnerabilities.






49. A black box test design technique in which test cases are designed to execute the combinations of inputs and/or stimuli (causes) shown in a decision table. [Veenendaal] See also decision table. A table showing combinations of inputs and/or stimuli (c






50. The capability of the software product to enable the user to understand whether the software is suitable - and how it can be used for particular tasks and conditions of use. [ISO 9126] See also usability. The capability of the software to be understo