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 based on an analysis of the internal structure of the component or system.






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






3. The process of transforming general testing objectives into tangible test conditions and test cases.






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






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






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






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






8. A discipline applying technical and administrative direction and surveillance to: identify and document the functional and physical characteristics of a configuration item - control changes to those characteristics - record and report change processi






9. A superior method or innovative practice that contributes to the improved performance of an organization under given context - usually recognized as 'best' by other peer organizations.






10. The process of running a test on the component or system under test - producing actual result(s).






11. A path that cannot be exercised by any set of possible input values.






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






13. A list of activities - tasks or events of the test process - identifying their intended start and finish dates and/or times - and interdependencies.






14. A sequence of one or more consecutive executable statements containing no branches. Note: A node in a control flow graph represents a basic block.






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






16. A diagram that depicts the states that a component or system can assume - and shows the events or circumstances that cause and/or result from a change from one state to another. [IEEE 610]






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






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






19. Testing the changes to an operational system or the impact of a changed environment to an operational system.






20. The degree to which a component - system or process meets specified requirements and/or user/customer needs and expectations. [After IEEE 610]






21. The capability of the software to be understood - learned - used and attractive to the user when used under specified conditions. [ISO 9126]






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






23. A test tool to perform automated test comparison of actual results with expected results.






24. A data item that specifies the location of another data item; for example - a data item that specifies the address of the next employee record to be processed. [IEEE 610]






25. The degree to which a component or system has a design and/or internal structure that is difficult to understand - maintain and verify. See also cyclomatic complexity. The number of independent paths through a program. Cyclomatic complexity is define






26. A development life cycle where a project is broken into a series of increments - each of which delivers a portion of the functionality in the overall project requirements. The requirements are prioritized and delivered in priority order in the approp






27. The process of testing to determine the reliability of a software product.






28. A subset of all defined/planned test cases that cover the main functionality of a component or system - to ascertaining that the most crucial functions of a program work - but not bothering with finer details. A daily build and smoke test is among in






29. A test design technique in which a model of the statistical distribution of the input is used to construct representative test cases. See also operational profile testing. Statistical testing using a model of system operations (short duration tasks)






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






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






32. An attribute of a component or system specified or implied by requirements documentation (for example reliability - usability or design constraints). [After IEEE 1008]






33. Modification of a software product after delivery to correct defects - to improve performance or other attributes - or to adapt the product to a modified environment. [IEEE 1219]






34. The tracing of requirements for a test level through the layers of test documentation (e.g. test plan - test design specification - test case specification and test procedure specification or test script).






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






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






37. Environmental and state conditions that must be fulfilled after the execution of a test or test procedure.






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






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






40. The calculated approximation of a result (e.g. effort spent - completion date - costs involved - number of test cases - etc.) which is usable even if input data may be incomplete - uncertain - or noisy.






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






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






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






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






45. The criteria used to (temporarily) stop all or a portion of the testing activities on the test items. [After IEEE 829]






46. Supplied instructions on any suitable media - which guides the installer through the installation process. This may be a manual guide - step-by-step procedure - installation wizard - or any other similar process description.






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






48. A document that specifies - ideally in a complete - precise and verifiable manner - the requirements - design - behavior - or other characteristics of a component or system - and - often - the procedures for determining whether these provisions have






49. A group of test activities that are organized and managed together. A test level is linked to the responsibilities in a project. Examples of test levels are component test - integration test - system test and acceptance test. [After TMap]






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







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