Showing posts with label L. Show all posts
Showing posts with label L. Show all posts
low level test case
A test case with concrete (implementation level) values for input d and expected results. Logical operators from high level test cases are replaced by actual values that correspond to the objectives of the logical operators. See also high level test case.
load testing tool
A tool to support load testing whereby it can simulate increasing load, e.g., numbers of concurrent users and/or transactions within a specified time-period. See also performance testing tool.
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 .
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.
lifecycle model
A partitioning of the life of a product or project into phases. [CMMI] See also software lifecycle.
learning (IDEAL)
The phase within the IDEAL model where one learns from experiences and improves one’s ability to adopt new processes and technologies in the future. The learning phase consists of the activities analyze and validate, and propose future actions. See also IDEAL . level test plan A test plan that typically addresses one test level. See also test plan.
learnability
The capability of the software product to enable the user to learn its application. [ISO 9126] See also usability.
lead assessor
The person who leads an assessment. In some cases, for instance CMMi and TMMi when formal assessments are conducted, the lead assessor must be accredited and formally trained.
LCSAJ
A Linear Code Sequence And Jump, consists 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.
Subscribe to:
Posts (Atom)