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. The activity of establishing or updating a test plan.






2. A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria. [After IEEE 829]






3. A high-level description of the test levels to be performed and the testing within those levels for an organization or programme (one or more projects).






4. The ability of the software product to perform its required functions under stated conditions for a specified period of time - or for a specified number of operations. [ISO 9126]






5. An informal test design technique where the tester actively controls the design of the tests as those tests are performed and uses information gained while testing to design new and better tests. [After Bach]






6. Testing the changes to an operational system or the impact of a changed environment to an operational system.






7. Analysis of software artifacts - e.g. requirements or code - carried out without execution of these software artifacts.






8. The capability of the software product to maintain a specified level of performance in cases of software faults (defects) or of infringement of its specified interface. [ISO 9126] See also reliability - robustness. The ability of the software product






9. A black box test design technique in which test cases are designed to execute business procedures and processes. [TMap] See also procedure testing. Testing aimed at ensuring that the component or system can operate in conjunction with new or existing






10. An executable statement where a variable is assigned a value.






11. A software product that supports one or more test activities - such as planning and control - specification - building initial files and data - test execution and test analysis. [TMap] See also CAST. Acronym for Computer Aided Software Testing.






12. The percentage of sequences of N+1 transitions that have been exercised by a test suite. [Chow]






13. The process of testing to determine the maintainability of a software product.






14. Analysis of source code carried out without execution of that software.






15. The process of evaluating behavior - e.g. memory performance - CPU usage - of a system or component during execution. [After IEEE 610]






16. A tool that supports the validation of models of the software or system [Graham].






17. Testing of software used to convert data from existing systems for use in replacement systems.






18. The capability of the software product to be adapted for different specified environments without applying actions or means other than those provided for this purpose for the software considered. [ISO 9126] See also portability. The ease with which t






19. A test design technique where the experience of the tester is used to anticipate what defects might be present in the component or system under test as a result of errors made - and to design tests specifically to expose them.






20. The number or category assigned to an attribute of an entity by making a measurement. [ISO 14598]






21. The behavior predicted by the specification - or another source - of the component or system under specified conditions.






22. Procedure to derive and/or select test cases based on an analysis of the internal structure of a component or system.






23. A software tool used to carry out instrumentation.






24. A program point at which the control flow has two or more alternative routes. A node with two or more links to separate branches.






25. Testing to determine the ease by which users with disabilities can use a component or system. [Gerrard]






26. The method used to perform the actual test execution - either manual or automated.






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






28. A test result in which a defect is reported although no such defect actually exists in the test object.






29. The percentage of condition outcomes that have been exercised by a test suite. 100% condition coverage requires each single condition in every decision statement to be tested as True and False.






30. (1) A standard against which measurements or comparisons can be made. (2) A test that is be used to compare components or systems to each other or to a standard as in (1). [After IEEE 610]






31. The degree to which a system or component accomplishes its designated functions within given constraints regarding processing time and throughput rate. [After IEEE 610] See also efficiency. The capability of the software product to provide appropriat






32. A development life cycle where a project is broken into a series of increments - each of which delivers a portion of the functionality in the overall project requirements. The requirements are prioritized and delivered in priority order in the approp






33. A black box test design technique in which test cases - described by means of a classification tree - are designed to execute combinations of representatives of input and/or output domains. [Grochtmann]






34. Any event occurring that requires investigation. [After IEEE 1008]






35. Procedure used to derive and/or select test cases.






36. Supplied instructions on any suitable media - which guides the installer through the installation process. This may be a manual guide - step-by-step procedure - installation wizard - or any other similar process description.






37. The capability of the software product to avoid unexpected effects from modifications in the software. [ISO 9126] See also maintainability. The ease with which a software product can be modified to correct defects - modified to meet new requirements






38. An element of configuration management - consisting of the evaluation - co-ordination - approval or disapproval - and implementation of changes to configuration items after formal establishment of their configuration identification. [IEEE 610]






39. An independent evaluation of software products or processes to ascertain compliance to standards - guidelines - specifications - and/or procedures based on objective criteria - including documents that specify: (1) the form or content of the products






40. The percentage of decision outcomes that have been exercised by a test suite. 100% decision coverage implies both 100% branch coverage and 100% statement coverage.






41. The process of assessing identified risks to estimate their impact and probability of occurrence (likelihood).






42. A group of people responsible for evaluating and approving or disapproving proposed changes to configuration items - and for ensuring implementation of approved changes. [IEEE 610]






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






44. The process of recognizing - investigating - taking action and disposing of defects. It involves recording defects - classifying them and identifying the impact. [After IEEE 1044]






45. An approach to testing in which test cases are designed based on descriptions and/or knowledge of business processes.






46. The number of independent paths through a program. Cyclomatic complexity is defined as: L - N + 2P - where - L = the number of edges/links in a graph - N = the number of nodes in a graph - P = the number of disconnected parts of the graph (e.g. a cal






47. A type of integration testing in which software elements - hardware elements - or both are combined all at once into a component or an overall system - rather than in stages. [After IEEE 610] See also integration testing. Testing performed to expose






48. A defect in a program's dynamic store allocation logic that causes it to fail to reclaim memory after it has finished using it - eventually causing the program to fail due to lack of memory.






49. Computer programs - procedures - and possibly associated documentation and data pertaining to the operation of a computer system. [IEEE 610]






50. A sequence of events - e.g. executable statements - of a component or system from an entry point to an exit point.