Glossary of Terms beginning Alphabet-I
Impact Analysis refers to the assessment of change to the layers of development documentation, test documentation and components, in order to implement a given change to specified requirements.
Incident refers to any event occurring during testing that requires investigation.
Incident Management refers to the process of recognizing, investigating, taking action and disposing of incidents. It involves recording incidents, classifying them and identifying the impact.
Incident Management Tool:
Incident Management Tool refers to a tool that facilitates the recording and status tracking of incidents found during testing. They often have workflow-oriented facilities to track and control the allocation, correction and re-testing of incidents and provide reporting facilities.
Incident Report is a document reporting on any event that occurs during the testing which requires investigation.
Incremental Development Model:
Incremental Development Model refers to 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 appropriate increment. In some (but not all) versions of this life cycle model, each subproject follows a �mini V-model� with its own design, coding and testing phases.
Incremental Integration Testing:
Incremental Integration Testing Involves continuous testing of an application while new functionality is simultaneously added. It requires that various aspects of an application’s functionality be independent enough to work separately before all parts of the program are completed. This testing is done either by programmers or by testers.
Independence means separation of responsibilities, which encourages the accomplishment of objective testing.
Independent Test Group (ITG):
Independent Test Group (ITG) is a group of people whose primary responsibility is software testing,
Inspection is a manual testing technique in which program documents like specifications, requirements, design, source code or user’s manuals are examined in a very formal and disciplined manner to discover errors, violations of standards and other problems. Checklists are a typical vehicle used in accomplishing this technique. It is a formal assessment of a product conducted by qualified independent. Inspection related to issues on deliverables involve the authors. The inspection is aimed at identification of defects, but it does not involve an action to rectify the defects. Authors take corrective actions and organize follow-up reviews as per the need.
Install / Uninstall Testing:
Install / Uninstall Testing involves testing of full, partial, or upgrade install / uninstall processes.
Installation Testing is performed to ensure that all the Installed features and options of the software are functioning properly. It confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions. The main objective of Installation Testing is to verify that all necessary components of the application are actually installed or not without missing out any component.
Intake Test refers to a special instance of a smoke test to decide if the component or system is ready for detailed and further testing. An intake test is typically carried out at the start of the test execution phase.
Integrity is a quality attribute pointing towards an extent to which unauthorized persons get prevented / controlled from accessing the software or its data.
Integration Testing refers to testing of the application after combining / integrating its various parts to find out if all parts function together correctly. The ‘parts’ can be code modules, individual applications, client and server applications on a network, etc. It begins after two or more programs or application components have been successfully unit tested. This type of testing is especially relevant to client/server and distributed systems. It is conducted by the development team to validate the interaction or communication between the individual components being integrated.
Interface Testing is the testing conducted to evaluate whether systems or components pass data and control correctly to one another.
Interoperability is a quality attribute pointing towards an effort required to couple one system with the other.
Interoperability Testing is the process of testing to determine the interoperability of a software product.
Invalid Case Testing:
Invalid Case Testing is a testing technique using erroneous [invalid, abnormal, or unexpected] input values or conditions. See: equivalence class partitioning.
Isolation Testing refers to the testing of individual components in isolation from surrounding components, with surrounding components being simulated by stubs and drivers, if needed.
I V & V:
I V & V means Independent Verification and Validation. Verification typically involves reviews and meetings to evaluate documents, plans, code, requirements, and specifications. Verification can be done with the help of checklists, issues lists, walkthroughs, and inspection meetings. Whereas Validation typically involves actual testing and takes place after verifications are completed.