1. Unit Testing
Unit testing is testing small, individual components of the software. It’s the first stage of testing, and while it’s usually done manually, it can be automated, so I wanted to include it here.

2. Smoke Tests
A smoke test is a functional test that determines whether or not a build is stable. It verifies the function of essential features to make sure the program can endure further testing. The name comes from the idea that this test prevents the program from catching fire if it’s not ready for additional testing.

3. Integration Tests
These functional tests make sure that all of the individual pieces of software test are well when operating as a whole. 

4. Regression Tests
Regression tests are both functional and non-functional, ensuring that no part of the software has regressed after changes are made. 

5. API Testing
The application programming interface or API acts as the conduit between all the other systems that your software needs to function. It’s usually tested after software development to make sure that everything is working together as it should.

6. Security Tests
Security tests are also functional and non-functional. Their purpose is to check everything for security weaknesses that can be exploited. 

7. Performance Tests
Non-functional performance tests evaluate stability and responsiveness. They ensure that the software can handle stress and deliver a better and more reliable user experience.

8. Acceptance Tests
Acceptance tests are functional tests that try to determine how end-users will respond to the final product. This test must be passed successfully before the product can be released to end-users. 

9. UI Tests
User interface tests are one of the last tests in the process. This test is designed to accurately replicate a typical user experience. It ensures that the end product that users interact with works as it should