interoperability testing:The process of testing to determine the interoperability of a software product.See also functionaliry testing. invalid testing:Testing using input values that should be rejected by the component or system.See also error tolerance ng isolation from surroundin tubs and dr ivers if item transmittal report:See release note. iterative development model:A development life cycle where a project is broken into a usually large number of iterations.An iteration is a complete development loop resulting in a release(interna K key performance indicator:See performance indicator. ng technique that uses tes expect but als keywor related the app eing teste supporting seripts that are called by the contro script LCSAJ:A Linear Code quence And Jump.consisting (conventionalyidcnti led y line nu e en control flow is transferred at the end of ear sequence,anc e nnear sequenc LCSAJ coverage:The percentage of LCSAJs of a component that have been exercised by a test suite.100%LCSAJ coverage implies 100%decision coverage. LCSAJ testing:A white box test design technique in which test cases are designed to execute LCSAJs. of the software product to enable the user to leam its application level test plan:A test plan that typically addresses one test level.See also testplan link testing:See component integration testing. load profile: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 ctions in a specifie predefined operational profie.Seearre time period and according to a load testing A type testing t o em with in of transactions,to determine what load can be handled by the component or system.See also performance testing.stress testing. logic-coverage testing:See white box testing.[Myers] logic-driven testing:See white box testing. logical test case:See high level test case22 interoperability testing: The process of testing to determine the interoperability of a software product. See also functionality testing. invalid testing: Testing using input values that should be rejected by the component or system. See also error tolerance. isolation testing: Testing of individual components in isolation from surrounding components, with surrounding components being simulated by stubs and drivers, if needed. item transmittal report: See release note. iterative development model: A development life cycle where a project is broken into a usually large number of iterations. An iteration is a complete development loop resulting in a release (internal or external) of an executable product, a subset of the final product under development, which grows from iteration to iteration to become the final product. K key performance indicator: See performance indicator. keyword driven testing: 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 script for the test. See also data driven testing. L LCSAJ: A Linear Code Sequence And Jump, consisting of the following three items (conventionally identified by line numbers in a source code listing): the start of the linear sequence of executable statements, the end of the linear sequence, and the target line to which control flow is transferred at the end of the linear sequence. LCSAJ coverage: The percentage of LCSAJs of a component that have been exercised by a test suite. 100% LCSAJ coverage implies 100% decision coverage. LCSAJ testing: A white box test design technique in which test cases are designed to execute LCSAJs. learnability: The capability of the software product to enable the user to learn its application. [ISO 9126] See also usability. level test plan: A test plan that typically addresses one test level. See also test plan. link testing: See component integration testing. load profile: 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 to a predefined operational profile. See also operational profile. load testing: 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 also performance testing, stress testing. logic-coverage testing: See white box testing. [Myers] logic-driven testing: See white box testing. logical test case: See high level test case