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.