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. Testing the attributes of a component or system that do not relate to functionality - e.g. reliability - efficiency - usability - maintainability and portability.






2. A model structure wherein attaining the goals of a set of process areas establishes a maturity level; each level builds a foundation for subsequent levels. [CMMI]






3. (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






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






5. A type of performance testing conducted to evaluate a system or component at or beyond the limits of its anticipated or specified work loads - or with reduced availability of resources such as access to memory or servers. [After IEEE 610] See also pe






6. A human action that produces an incorrect result. [After IEEE 610]






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






8. Non fulfillment of a specified requirement. [ISO 9000]






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






10. A method to determine test suite thoroughness by measuring the extent to which a test suite can discriminate the program from slight variants (mutants) of the program.






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






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.






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






14. The process of testing an integrated system to verify that it meets specified requirements. [Hetzel]






15. The process of transforming general testing objectives into tangible test conditions and test cases.






16. A program of activities designed to improve the performance and maturity of the organization's processes - and the result of such a program. [CMMI]






17. A Linear Code Sequence And Jump - consisting of the following three items (conventionally identified by line numbers in a source code listing): the start of the linear sequence of executable statements - the end of the linear sequence - and the targe






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






19. The process of testing to determine the functionality of a software product.






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






21. The degree to which a component or system is operational and accessible when required for use. Often expressed as a percentage. [IEEE 610]






22. A software tool that translates programs expressed in a high order language into their machine language equivalents. [IEEE 610]






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






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






25. An expert based test estimation technique that aims at making an accurate estimation using the collective wisdom of the team members.






26. A document specifying a set of test cases (objective - inputs - test actions - expected results - and execution preconditions) for a test item. [After IEEE 829]






27. A memory access defect due to the attempt by a process to store data beyond the boundaries of a fixed length buffer - resulting in overwriting of adjacent memory areas or the raising of an overflow exception. See also buffer. A device or storage area






28. The physical or functional manifestation of a failure. For example - a system in failure mode may be characterized by slow operation - incorrect outputs - or complete termination of execution. [IEEE 610]






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






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






31. The process of identifying risks using techniques such as brainstorming - checklists and failure history.






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






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






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






35. Computer instructions and data definitions expressed in a programming language or in a form output by an assembler - compiler or other translator. [IEEE 610]






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






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






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






39. The ratio of the number of failures of a given category to a given unit of measure - e.g. failures per unit of time - failures per number of transactions - failures per number of computer runs. [IEEE 610]






40. Acronym for Computer Aided Software Engineering.






41. A measurement scale and the method used for measurement. [ISO 14598]






42. The capability of the software product to be used in place of another specified software product for the same purpose in the same environment. [ISO 9126] See also portability. The ease with which the software product can be transferred from one hardw






43. The evaluation of a condition to True or False.






44. The testing of individual software components. [After IEEE 610]






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






46. The process of recognizing - investigating - taking action and disposing of incidents. It involves logging incidents - classifying them and identifying the impact. [After IEEE 1044]






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






48. Deviation of the component or system from its expected delivery - service or result. [After Fenton]






49. A high level document describing the principles - approach and major objectives of the organization regarding testing.






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