Functional Testing: Focuses on ensuring that the software functions according to the requirements. Example: Verifying that a login form correctly accepts user credentials. Regression Testing: Conducted to ensure that new changes (such as code fixes or features) do not negatively impact the existing functionality. Example: After adding a new feature, testing all previous features to ensure they still work. Integration Testing: Focuses on testing how different parts of the system work together. Example: Testing how the user registration system interacts with the database. Smoke Testing: Basic checks that ensure the core features of the software are working (also known as build verification testing). Example: Checking if the app launches and displays the homepage. Sanity Testing: Conducted after receiving a new build to verify that a specific bug has been fixed or that a specific functionality is working. User Acceptance Testing (UAT): Performed by end-users to confirm the software meets business needs. Example: A client verifying if the CRM system fulfills their business process.