| Unit Testing |
A programmatic test that tests the internal working of a unit of code, such as a method or a function. |
| Integration Testing |
Ensures that multiple components of systems work as expected when they are combined to produce a result. |
| Regression Testing |
Ensures that existing features/functionality that used to work are not broken due to new code changes. |
| System Testing |
Complete end-to-end testing is done on the complete software to make sure the whole system works as expected. |
| Smoke Testing |
A quick test performed to ensure that the software works at the most basic level and doesn’t crash when it’s started. Its name originates from the hardware testing where you just plug the device and see if smoke comes out. |
| Performance Testing |
Ensures that the software performs according to the user’s expectations by checking the response time and throughput under specific load and environment. |
| User-Acceptance Testing |
Ensures the software meets the requirements of the clients or users. This is typically the last step before the software is live, i.e. it goes to production. |
| Stress Testing |
Ensures that the performance of the software doesn’t degrade when the load increases. In stress testing, the tester subjects the software under heavy loads, such as a high number of requests or stringent memory conditions to verify if it works well. |
| Usability Testing |
Measures how usable the software is. This is typically performed with a sample set of end-users, who use the software and provide feedback on how easy or complicated it is to use the software. |
| Security Testing |
Now more important than ever. Security testing tries to break a software’s security checks, to gain access to confidential data. Security testing is crucial for web-based applications or any applications that involve money. |
