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 carried out informally; no formal test preparation takes place - no recognized test design technique is used - there are no expectations for results and arbitrariness guides the test execution activity.






2. A logical expression that can be evaluated as True or False - e.g. A>B. See also test condition. 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






3. A white box test design technique in which test cases are designed to execute condition outcomes.






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






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






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






7. The response of a component or system to a set of input values and preconditions.






8. Testing - either functional or non-functional - without reference to the internal structure of the component or system. Black-box test design technique Procedure to derive and/or select test cases based on an analysis of the specification - either fu






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






10. A requirement that specifies a function that a component or system must perform. [IEEE 610]






11. The process of testing to determine the efficiency of a software product.






12. A technique used to analyze the causes of faults (defects). The technique visually models how logical relationships between failures - human errors - and external events can combine to cause specific faults to disclose.






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






14. A test is deemed to fail if its actual result does not match its expected result.






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






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






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






18. Testing of individual components in isolation from surrounding components - with surrounding components being simulated by stubs and drivers - if needed.






19. The capability of the software product to provide appropriate performance - relative to the amount of resources used under stated conditions. [ISO 9126]






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. Procedure used to derive and/or select test cases.






22. A scheme for the execution of test procedures. The test procedures are included in the test execution schedule in their context and in the order in which they are to be executed.






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






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






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






26. The process of testing to determine the resource-utilization of a software product. See also efficiency testing. The process of testing to determine the efficiency of a software product.






27. During the test closure phase of a test process data is collected from completed activities to consolidate experience - testware - facts and numbers. The test closure phase consists of finalizing and archiving the testware and evaluating the test pro






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






29. A set of test cases derived from the internal structure of a component or specification to ensure that 100% of a specified coverage criterion will be achieved.






30. Analysis of software artifacts - e.g. requirements or code - carried out without execution of these software artifacts.






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






32. A black box test design technique where test cases are selected - possibly using a pseudo-random generation algorithm - to match an operational profile. This technique can be used for testing non-functional attributes such as reliability and performa






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






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. The process of finding - analyzing and removing the causes of failures in software.






36. A tool that supports the test design activity by generating test inputs from a specification that may be held in a CASE tool repository - e.g. requirements management tool - from specified test conditions held in the tool itself - or from code.






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






38. A test plan that typically addresses one test phase. See also test plan. 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 testin






39. An incremental approach to integration testing where the lowest level components are tested first - and then used to facilitate the testing of higher level components. This process is repeated until the component at the top of the hierarchy is tested






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






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






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






43. A document summarizing testing activities and results. It also contains an evaluation of the corresponding test items against exit criteria. [After IEEE 829]






44. Testing the quality of the documentation - e.g. user guide or installation guide.






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






46. A device - computer program or system used during testing - which behaves or operates like a given system when provided with a set of controlled inputs. [After IEEE 610 - DO178b] See also emulator. A device - computer program - or system that accepts






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






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






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






50. An entity or property used as a basis for test coverage - e.g. equivalence partitions or code statements.







Sorry!:) No result found.

Can you answer 50 questions in 15 minutes?


Let me suggest you:

Browse all subjects

Browse all tests

Most popular tests



Major Subjects

Tests & Exams


AP
CLEP
DSST
GRE
SAT
GMAT

Browse all subjects

Browse all tests

Most popular tests