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 program element is said to be exercised by a test case when the input value causes the execution of that element - such as a statement - decision - or other structural element.






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






3. Commonly used to refer to a test procedure specification - especially an automated one.






4. The insertion of additional code into the program in order to collect information about program behavior during execution - e.g. for measuring code coverage.






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






6. Definition of user profiles in performance - load and/or stress testing. Profiles should reflect anticipated or actual usage based on an operational profile of a component or system - and hence the expected workload. See also load profile - operation






7. A white box test design technique in which test cases are designed to execute definition and use pairs of variables.






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






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






10. A software tool used to carry out instrumentation.






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






12. A device - computer program - or system that accepts the same inputs and produces the same outputs as a given system. [IEEE 610] See also simulator. A device - computer program or system used during testing - which behaves or operates like a given sy






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






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






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






16. A tool that supports operational security.






17. A test management task that deals with the activities related to periodically checking the status of a test project. Reports are prepared that compare the actuals to that which was planned. See also test management. The planning - estimating - monito






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






19. Procedure used to derive and/or select test cases.






20. Operational testing in the acceptance test phase - typically performed in a simulated real-life operational environment by operator and/or administrator focusing on operational aspects - e.g. recoverability - resource-behavior - installability and te






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






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






23. The function to check on the contents of libraries of configuration items - e.g. for standards compliance. [IEEE 610]






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






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






26. A test plan that typically addresses one test level. 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






27. A white box test design technique in which test cases are designed to execute branches.






28. Testing to determine the ease by which users with disabilities can use a component or system. [Gerrard]






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






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






31. A specification of the activity which a component or system being tested may experience in production. A load profile consists of a designated number of virtual users who process a defined set of transactions in a specified time period and according






32. A test plan that typically addresses multiple test levels. 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






33. A 2-dimensional array constructed with special mathematical properties - such that choosing any two columns in the array provides every pair combination of each number in the array.






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






35. A software component or test tool that replaces a component that takes care of the control and/or the calling of a component or system. [After TMap]






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






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






38. Execution of the test process against a single identifiable release of the test object.






39. The effect on the component or system by the measurement instrument when the component or system is being measured - e.g. by a performance testing tool or monitor. For example performance may be slightly worse when performance testing tools are being






40. Testing using input values that should be rejected by the component or system. See also error tolerance. The ability of a system or component to continue normal operation despite the presence of erroneous inputs. [After IEEE 610].






41. Testing to determine the safety of a software product.






42. The set of generic and specific conditions - agreed upon with the stakeholders - for permitting a process to be officially completed. The purpose of exit criteria is to prevent a task from being considered completed when there are still outstanding p






43. The process of finding - analyzing and removing the causes of failures in software.






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






45. A feature or characteristic that affects an item's quality. [IEEE 610]






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






47. A test result which fails to identify the presence of a defect that is actually present in the test object.






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






49. A special instance of a smoke test to decide if the component or system is ready for detailed and further testing. An intake test is typically carried out at the start of the test execution phase. See also smoke test. A subset of all defined/planned






50. The capability of the software product to re-establish a specified level of performance and recover the data directly affected in case of failure. [ISO 9126] See also reliability. The ability of the software product to perform its required functions







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