Unit Testing
- Unit testing is a method by which individual units of source code are tested to determine if they are fit for use.
- Unit tests are created by programmers or occasionally by white box testers during the development process.
Integration testing
- Individual software modules are combined and tested as a group.
- System integration testing is the process of verifying the synchronization between two or more software systems and which can be performed after software system collaboration is completed.
- It occurs after unit testing and before system testing
- The purpose of integration testing is to verify functional, performance, and reliability requirements placed on major design items
System testing
- Once the system testing is done the software is ready to ship
- Done by QA at development end
- System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.
- It is also intended to test up to and beyond the bounds defined in the software/hardware requirements specification(s).
UAT
- User acceptance testing is testing conducted by users of the system
- Done by QA(trained like end users
Smoke testing
- Smoke testing refers to the first test made after assembly or repairs to a system, to provide some assurance that the system under test will not catastrophically fail. After a smoke test proves that "the pipes will not leak, the keys seal properly, the circuit will not burn, or the software will not crash outright," the system is ready for more stressful testing.
Source: Wikipedia
- Unit testing is a method by which individual units of source code are tested to determine if they are fit for use.
- Unit tests are created by programmers or occasionally by white box testers during the development process.
Integration testing
- Individual software modules are combined and tested as a group.
- System integration testing is the process of verifying the synchronization between two or more software systems and which can be performed after software system collaboration is completed.
- It occurs after unit testing and before system testing
- The purpose of integration testing is to verify functional, performance, and reliability requirements placed on major design items
System testing
- Once the system testing is done the software is ready to ship
- Done by QA at development end
- System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system's compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic.
- It is also intended to test up to and beyond the bounds defined in the software/hardware requirements specification(s).
UAT
- User acceptance testing is testing conducted by users of the system
- Done by QA(trained like end users
Smoke testing
- Smoke testing refers to the first test made after assembly or repairs to a system, to provide some assurance that the system under test will not catastrophically fail. After a smoke test proves that "the pipes will not leak, the keys seal properly, the circuit will not burn, or the software will not crash outright," the system is ready for more stressful testing.
Source: Wikipedia
