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 portion of an input or output domain for which the behavior of a component or system is assumed to be the same - based on the specification.






2. A peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. [Gilb and Graham - IEEE 1028] See also peer review. A review of a software work product by colleagues of the producer of the product for the p






3. Software developed specifically for a set of users or customers. The opposite is off-the-shelf software.






4. A test case that cannot be executed because the preconditions for its execution are not fulfilled.






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






6. Confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled. [ISO 9000]






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






8. The degree of uniformity - standardization - and freedom from contradiction among the documents or parts of a component or system. [IEEE 610]






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






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






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






12. The planning - estimating - monitoring and control of test activities - typically carried out by a test manager.






13. A software tool or hardware device that runs concurrently with the component or system under test and supervises - records and/or analyses the behavior of the component or system. [After IEEE 610]






14. A black box test design technique in which test cases are designed from cause-effect graphs. [BS 7925/2]






15. A tool that supports stress testing.






16. A group of test activities aimed at testing a component or system focused on a specific test objective - i.e. functional test - usability test - regression test etc. A test type may take place on one or more test levels or test phases. [After TMap]






17. A set of one or more test cases. [IEEE 829]






18. The first executable statement within a component.






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






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






21. A type of test tool that enables data to be selected from existing databases or created - generated - manipulated and edited for use in testing.






22. A document produced at the end of the test process summarizing all testing activities and results. It also contains an evaluation of the test process and lessons learned.






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






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






25. A collection of components organized to accomplish a specific function or set of functions. [IEEE 610]






26. A type of performance testing conducted to evaluate the behavior of a component or system with increasing load - e.g. numbers of parallel users and/or numbers of transactions - to determine what load can be handled by the component or system. See als






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






28. A white box test design technique in which test cases are designed to execute LCSAJs.






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






30. Procedure to derive and/or select test cases based on an analysis of the specification - either functional or non-functional - of a component or system without reference to its internal structure.






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






32. Testing practice for a project using agile methodologies - such as extreme programming (XP) - treating development as the customer of testing and emphasizing the test first design paradigm. See also test driven development. A way of developing softwa






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






34. A document specifying the test conditions (coverage items) for a test item - the detailed test approach and identifying the associated high level test cases. [After IEEE 829]






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






36. A tool used to check that no brtoken hyperlinks are present on a web site.






37. Method aiming to measure the size of the functionality of an information system. The measurement is independent of the technology. This measurement may be used as a basis for the measurement of productivity - the estimation of the needed resources -






38. A meeting at the end of a project during which the project team members evaluate the project and learn lessons that can be applied to the next project.






39. The person responsible for project management of testing activities and resources - and evaluation of a test object. The individual who directs - controls - administers - plans and regulates the evaluation of a test object.






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






41. A scale that constrains the type of data analysis that can be performed on it. [ISO 14598]






42. The process of testing to determine the interoperability of a software product.






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






44. A series which appears to be random but is in fact generated according to some prearranged sequence.






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






46. 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. See also incid






47. A model that shows the growth in reliability over time during continuous testing of a component or system as a result of the removal of defects that result in reliability failures.






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






49. Confirmation by examination and through provision of objective evidence that specified requirements have been fulfilled. [ISO 9000]






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