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 percentage of sequences of N+1 transitions that have been exercised by a test suite. [Chow]






2. A development life cycle where a project is broken into a usually large number of iterations. An iteration is a complete development loop resulting in a release (internal or external) of an executable product - a subset of the final product under dev






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






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






5. A document identifying test items - their configuration - current status and other delivery information delivered by development to testing - and possibly other stakeholders - at the start of a test execution phase. [After IEEE 829]






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






7. Comparison of actual and expected results - performed while the software is being executed - for example by a test execution tool.






8. An environment containing hardware - instrumentation - simulators - software tools - and other support elements needed to conduct a test. [After IEEE 610]






9. The process of intentionally adding known defects to those already in the component or system for the purpose of monitoring the rate of detection and removal - and estimating the number of remaining defects. [IEEE 610]






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






11. Coordinated activities to direct and control an organization with regard to quality. Direction and control with regard to quality generally includes the establishment of the quality policy and quality objectives - quality planning - quality control -






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






13. Procedure to derive and/or select test cases based on an analysis of the specification of the functionality of a component or system without reference to its internal structure. See also black box test design technique. Procedure to derive and/or sel






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






15. The person involved in the review that identifies and describes anomalies in the product or project under review. Reviewers can be chosen to represent different viewpoints and roles in the review process.






16. An abstract representation of the sequence and possible changes of the state of data objects - where the state of an object is any of: creation - usage - or destruction. [Beizer]






17. A minimal software item that can be tested in isolation.






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






19. A pointer within a web page that leads to other web pages.






20. An integration approach that combines the components or systems for the purpose of getting a basic functionality working early. See also integration testing. Testing performed to expose defects in the interfaces and in the interactions between integr






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






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






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






24. A black box test design technique in which test cases are designed based upon the definition of the input domain and/or output domain.






25. A procedure to derive and/or select test cases targeted at one or more defect categories - with tests being developed from what is known about the specific defect category. See also defect taxonomy. A system of (hierarchical) categories designed to b






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






27. The capability of the software product to provide functions which meet stated and implied needs when the software is used under specified conditions. [ISO 9126]






28. An instance of an output. See also output.A variable (whether stored within a component or outside) that is written by a component.






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






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






31. A variable (whether stored within a component or outside) that is written by a component.






32. A variable (whether stored within a component or outside) that is read by a component.






33. A factor that could result in future negative consequences; usually expressed as impact and likelihood.






34. An extension of FMEA - as in addition to the basic FMEA - it includes a criticality analysis - which is used to chart the probability of failure modes against the severity of their consequences. The result highlights failure modes with relatively hig






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






36. A document summarizing testing activities and results - produced at regular intervals - to report progress of testing activities against a baseline (such as the original test plan) and to communicate risks and alternatives requiring a decision to man






37. A formula based test estimation method based on function point analysis. [TMap]






38. A table showing combinations of inputs and/or stimuli (causes) with their associated outputs and/or actions (effects) - which can be used to design test cases.






39. A tool that provides support for the identification and control of configuration items - their status over changes and versions - and the release of baselines consisting of configuration items.






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






41. A software tool used to carry out instrumentation.






42. A programming language in which executable test scripts are written - used by a test execution tool (e.g. a capture/playback tool).






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






44. The process of developing and prioritizing test procedures - creating test data and - optionally - preparing test harnesses and writing automated test scripts.






45. A review characterized by documented procedures and requirements - e.g. inspection.






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






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






48. The process of assigning a number or category to an entity to describe an attribute of that entity. [ISO 14598]






49. Tests aimed at showing that a component or system does not work. Negative testing is related to the testers' attitude rather than a specific test approach or test design technique - e.g. testing with invalid input values or exceptions. [After Beizer]






50. The capability of the software product to use appropriate amounts and types of resources - for example the amounts of main and secondary memory used by the program and the sizes of required temporary or overflow files - when the software performs its