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. A document describing the scope - approach - resources and schedule of intended test activities. It identifies amongst others test items - the features to be tested - the testing tasks - who will do each task - degree of tester independence - the tes






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






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






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






5. A path by which the original input to a process (e.g. data) can be traced back through the process - taking the process output as a starting point. This facilitates defect analysis and allows a process audit to be carried out. [After TMap]






6. A five level staged framework for test process improvement - related to the Capability Maturity Model Integration (CMMI) - that describes the key elements of an effective test process.






7. A test whereby real-life users are involved to evaluate the usability of a component or system.






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






9. Coverage measures based on the internal structure of a component or system.






10. A document that consists of a test design specification - test case specification and/or test procedure specification.






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






12. The criteria used to (temporarily) stop all or a portion of the testing activities on the test items. [After IEEE 829]






13. A statement which - when compiled - is translated into object code - and which will be executed procedurally when the program is running and may perform an action on data.






14. Testing the attributes of a component or system that do not relate to functionality - e.g. reliability - efficiency - usability - maintainability and portability.






15. The set from which valid input and/or output values can be selected.






16. A black box test design technique in which test cases are designed to execute all possbile discrete combinations of each pair of input parameters. See also orthogonal array testing. A systematic way of testing all-pair combinations of variables using






17. Testware used in automated testing - such as tool scripts.






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






19. A white box test design technique in which test cases are designed to execute decision outcomes.






20. The data received from an external source by the test object during test execution. The external source can be hardware - software or human.






21. A scripting technique that uses data files to contain not only test data and expected results - but also keywords related to the application being tested. The keywords are interpreted by special supporting scripts that are called by the control scrip






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






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






24. A superior method or innovative practice that contributes to the improved performance of an organization under given context - usually recognized as 'best' by other peer organizations.






25. (1) The capability of an organization with respect to the effectiveness and efficiency of its processes and work practices. See also Capability Maturity Model - Test Maturity Model. (2) The capability of the software product to avoid failure as a res






26. Testing that involves the execution of the software of a component or system.






27. A black box test design technique in which test cases are designed to execute valid and invalid state transitions. See also N-switch testing. A form of state transition testing in which test cases are designed to execute all valid sequences of N+1 tr






28. A chronological record of relevant details about the execution of tests. [IEEE 829]






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






30. The percentage of definition-use pairs that have been exercised by a test suite.






31. A set of several test cases for a component or system under test - where the post condition of one test is often used as the precondition for the next one.






32. A black box test design technique in which test cases are designed based on boundary values. See also boundary value. An input value or output value which is on the edge of an equivalence partition or at the smallest incremental distance on either si






33. Choosing a set of input values to force the execution of a given path.






34. A test approach in which the test suite comprises all combinations of input values and preconditions.






35. A static usability test technique to determine the compliance of a user interface with recognized usability principles (the so-called "heuristics").






36. The process of testing to determine the reliability of a software product.






37. The degree to which a component or system has a design and/or internal structure that is difficult to understand - maintain and verify. See also cyclomatic complexity. The number of independent paths through a program. Cyclomatic complexity is define






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






39. Testing conducted to evaluate a component or system in its operational environment. [IEEE 610]






40. A tool that provides support to the review process. Typical features include review planning and tracking support - communication support - collaborative reviews and a repository for collecting and reporting of metrics.






41. Procedure to derive and/or select test cases for nonfunctional testing based on an analysis of the specification of a component or system without reference to its internal structure. See also black box test design technique. Procedure to derive and/o






42. A test is deemed to pass if its actual result matches its expected result.






43. Testing of software or specification by manual simulation of its execution. See also static analysis. Analysis of software artifacts - e.g. requirements or code - carried out without execution of these software artifacts.






44. A type of test execution tool where inputs are recorded during manual testing in order to generate automated test scripts that can be executed later (i.e. replayed). These tools are often used to support automated regression testing.






45. Environmental and state conditions that must be fulfilled after the execution of a test or test procedure.






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






47. The capability of the software product to enable the user to operate and control it. [ISO 9126] See also usability. The capability of the software to be understood - learned - used and attractive to the user when used under specified conditions. [ISO






48. The degree - expressed as a percentage - to which a specified coverage item has been exercised by a test suite.






49. Data that exists (for example - in a database) before a test is executed - and that affects or is affected by the component or system under test.






50. A path for which a set of input values and preconditions exists which causes it to be executed.