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 which are exercised by a test case suite.

LCSAJ Testing: A test case design technique for a component in which test cases are designed to execute LCSAJs.

Logic-Coverage Testing: Sometimes referred to as Path Testing, logic-coverage testing attempts to expose software defects by exercising a unique combination of the program's statements known as a Path.

Load Testing: The process of creating demand on a system or device and measuring its response. Load testing generally refers to the practice of modeling the expected usage of a software program by simulating multiple users accessing the program's services concurrently. As such, this testing is most relevant for multi-user systems, often one built using a client/server model, such as web servers. However, other types of software systems can be load tested also. For example, a word processor or graphics editor can be forced to read an extremely large document; or a financial package can be forced to generate a report based on several years' worth of data. The most accurate load testing occurs with actual, rather than theoretical, results. See also Concurrent Testing, Performance Testing, Reliability Testing, and Volume Testing.

Localization Testing: This term refers to making software specifically designed for a specific locality. This test is based on the results of globalization testing, which verifies the functional support for that particular culture/locale. Localization testing can be executed only on the localized version of a product.

The test effort during localization testing focuses on:

• Areas affected by localization, such as UI and content
• Culture/locale-specific, language-specific, and region-specific areas.

In addition, localization testing should include:

• Basic functionality tests
• Setup and upgrade tests run in the localized environment
• Plan application and hardware compatibility tests according to the product's target region.

Log: A chronological record of relevant details about the execution of tests.

Loop Testing: Loop testing is the testing of a resource or resources multiple times under program control.

K

KBS (Knowledge Based System): A domain specific knowledge base combined with an inference engine that processes knowledge encoded in the knowledge base to respond to a user's request for advice.

Key Performance Indicator: Quantifiable measurements against which specific performance criteria can be set.

Keyword Driven Testing: An approach to test script writing aimed at code based automation tools that separated much of the programming work from the actual test steps. The results is the test steps can be designed earlier and the code base if often easier to read and maintain.

Knowledge Engineering: The process of codifying an expert's knowledge in a form that can be accessed through an expert system.

Known Error: An incident or problem for which the root cause is known and for which a temporary Work-around or a permanent alternative has been identified.

J

I

ITIL (IT Infrastructure Library): A consistent and comprehensive documentation of best practice for IT Service Management, ITIL consists of a series of books giving guidance on the provision of quality IT services, and on the accommodation and environmental facilities needed to support IT.

Implementation Testing: See Installation Testing.

Incremental Testing: Partial testing of an incomplete product. The goal of incremental testing is to provide an early feedback to software developers.

Independence: Separation of responsibilities which ensure the accomplishment of objective evaluation.

Independent Test Group (ITG): A group of people whose primary responsibility is to conduct software testing for other companies.

Infeasible Path: A path which cannot be exercised by any set of possible input values.

Inference: Forming a conclusion from existing facts.

Inference Engine: Software that provides the reasoning mechanism in an expert system. In a rule based expert system, typically implements forward chaining and backward chaining strategies.

Infrastructure: The organizational artifacts needed to perform testing, consisting of test environments, Automated Test Tools, office environment and procedures.

Inheritance: The ability of a class to pass on characteristics and data to its descendants.

Input: A variable (whether stored within a component or outside it) that is read by the component.

Input Domain: The set of all possible inputs.

Inspection: A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement.

Installability: The ability to a software Component or system to be installed on a defined target platform allowing it to be run as required. Installation includes both a new installation and an upgrade.

Installability Testing: Testing whether the software or system installation being tested meets predefined installation requirements.

Installation Guide: Supplies instructions on any suitable media, which guides the installer trough the installation process. This may be a manual guide, step-by-step procedure, installation wizard, or any other similar process description.

Installation Testing: Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Event can include shortage of disk space, unexpected loss of communication, or powder out conditions.
Such testing focuses on what customers will need to do to install and set up the new software successfully and is typically done by the software testing engineer in conjunction with the configuration manager. Implementation testing is usually defined as testing which places a complied version of code into the testing or pre-production environment, from which it may or may not progress into production. This generally takes place outside of the software development environment to limit code corruption from other future releases which may reside on the development network.

Installation Wizard: Supplies software on any suitable media, which leads the installer through the installation process. It shall normally run the installation process, provide feedback on installation outcomes and prompt for options.

Instrumentation: The insertion of additional code into the program in order to collect information about program behavior during program execution.

Integration: The process of combining components into larger groups or assemblies.

Integration Testing: Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

Interface Testing: Integration testing where the interfaces between system components are tested.

Isolation Testing: Component testing of individual components in isolation from surrounding components.

H

Harness: A test environment comprised to stubs and drivers needed to conduct a test.

Heuristics: The informal, judgement knowledge of an application area that constitutes the "rules of good judgement" in the field. Heuristics also encompass the knowledge of how to solve problems efficiently and effectively, how to plan steps in solving a complex problem, how to improve performance, etc.

High Order Tests: High-Order testing checks that the software meets customer requirements and that the software, along with other systems elements, meets the functional, behavioral, and performance requirements. It uses Black-Box techniques and requires an outsider perspective. Therefore, organizations often use an Independent Testing Group (ITG) or the users themselves to perform high-order testing.

High-order testing includes Validation Testing, System Testing (focusing on aspects such as reliability, security, stress, usability, and performance), and Acceptance Testing (includes alpha and beta testing). The testing strategy specifies the type of high-order testing that the project requires. This depends on the aspects that are important in a particular system from the user perspective.