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 evaluation of a condition to True or False.






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






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






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






5. An approach to testing in which test cases are designed based on test objectives and test conditions derived from requirements - e.g. tests that exercise specific functions or probe non-functional attributes such as reliability or usability.






6. A tool that provides objective measures of what structural elements - e.g. statements - branches have been exercised by a test suite.






7. A type of test tool that is able to execute other software using an automated test script - e.g. capture/playback. [Fewster and Graham]






8. A sequence of events (paths) in the execution through a component or system.






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






10. Recording the details of any incident that occurred - e.g. during testing.






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






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






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






14. An attribute of a test indicating whether the same results are produced each time the test is executed.






15. The process of testing to determine the interoperability of a software product. See also functionality testing. The process of testing to determine the functionality of a software product.






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






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






18. A risk directly related to the test object. See also risk. A factor that could result in future negative consequences; usually expressed as impact and likelihood.






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






20. A test basis document that can only be amended by a formal change control process. See also baseline. A specification or software product that has been formally reviewed or agreed upon - that thereafter serves as the basis for further development - a






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






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






23. Part of quality management focused on providing confidence that quality requirements will be fulfilled. [ISO 9000]






24. A software product that is developed for the general market - i.e. for a large number of customers - and that is delivered to many customers in identical format.






25. A framework to describe the software development life cycle activities from requirements specification to maintenance. The V-model illustrates how testing activities can be integrated into each phase of the software development life cycle.






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






27. A form of static analysis based on the definition and usage of variables.






28. Testing aimed at ensuring that the component or system can operate in conjunction with new or existing users' business procedures or operational procedures.






29. A tool to support performance testing and that usually has two main facilities: load generation and test transaction measurement. Load generation can simulate either multiple users or high volumes of input data. During execution - response time measu






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. A white box test design technique in which test cases are designed to execute LCSAJs.






32. A systematic evaluation of software acquisition - supply - development - operation - or maintenance process - performed by or on behalf of management that monitors progress - determines the status of plans and schedules - confirms requirements and th






33. Testing based on an analysis of the internal structure of the component or system.






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






35. The use of software - e.g. capture/playback tools - to control the execution of tests - the comparison of actual results to expected results - the setting up of test preconditions - and other test control and reporting functions.






36. An item or event of a component or system that could be verified by one or more test cases - e.g. a function - transaction - feature - quality attribute - or structural element.






37. A reason or purpose for designing and executing a test.






38. The process of demonstrating the ability to fulfill specified requirements. Note the term 'qualified' is used to designate the corresponding status. [ISO 9000]






39. A document reporting on any event that occurred - e.g. during the testing - which requires investigation. [After IEEE 829]






40. A tool that carries out static analysis.






41. A computational model consisting of a finite number of states and transitions between those states - possibly with accompanying actions. [IEEE 610]






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






43. The process of testing to determine the portability of a software product.






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






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






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






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






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






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






50. The capability of the software product to provide the right or agreed results or effects with the needed degree of precision. [ISO 9126] See also functionality testing. Testing based on an analysis of the specification of the functionality of a compo