Types of Software Testing

Hardware/software integration testing: To verify correct operation of the software in the target computer environment.
Software integration testing: To verify the interrelationships between software requirements and components and to verify the implementation of the software requirements and software components within the software architecture.
Low-level testing: To verify the implementation of software low-level requirements.

Objective of HSIT:
The objective of requirements-based hardware/software integration testing is to ensure that the software in the target computer will satisfy the high-level requirements.

Errors revealed by HSIT:
Incorrect interrupt handling.
Failure to satisfy execution time requirements.
Incorrect software response to hardware transients or hardware failures, for example, start-up sequencing, transient input loads and input power transients.
Data bus and other resource contention problems, for example, memory mapping.
Inability of built-in test to detect failures.
Errors in hardware/software interfaces.
Incorrect behavior of feedback loops.
Incorrect control of memory management hardware or other hardware devices under software control.
Stack overflow.
Incorrect operation of mechanism(s) used to confirm the correctness and compatibility of field-loadable software.
Violations of software partitioning

Objective of SIT:
The objective of requirements-based software integration testing is to ensure that the software components interact correctly with each other and satisfy the software requirements and software architecture.

Errors revealed by SIT
Incorrect initialization of variables and constants.
Parameter passing errors.
Data corruption, especially global data.
Inadequate end-to-end numerical resolution.
Incorrect sequencing of events and operations.

Objective of Low-Level testing:
The objective of requirements-based low-level testing is to ensure that the software components satisfy their low-level requirements.

Errors revealed by Low Level Testing
Failure of an algorithm to satisfy a software requirement.
Incorrect loop operations.
Incorrect logic decisions.
Failure to process correctly legitimate combinations of input conditions.
Incorrect responses to missing or corrupted input data.
Incorrect handling of exceptions, such as arithmetic faults or violations of array limits.
Incorrect computation sequence.
Inadequate algorithm precision, accuracy or performance.