What types of testing have you applied in your projects?

Applied the following types of testing:

Functional Testing:

• Unit Testing: Often wrote or reviewed tests within development tasks, especially when teams adhered to TDD.
• Integration Testing: Tested interactions between modules, services, databases.
• System Testing: Tested the system as a whole, verifying compliance with requirements.
• Acceptance Testing: Worked with business analysts or clients to verify if the product met expectations.

Non-Functional Testing:

• Load Testing: Checked system performance under various load levels using tools like JMeter, LoadRunner.
• Stress Testing: Determined system resilience to extreme loads.
• Stability Testing (Endurance Testing): Long-term testing to identify issues related to memory leaks or performance degradation over time.
• Security Testing: Conducted static and dynamic code analysis, fuzz testing, manual testing for XSS, SQL Injection, and other vulnerabilities.
• Usability Testing: Analyzed how intuitive and user-friendly the interface was for end-users.
• Compatibility Testing: Verified application operation across different environments (browsers, operating systems, devices).

Change Testing:

• Regression Testing: Ensured that new changes did not break existing functionality. Automation of this testing was a priority.
• Sanity Check / Smoke Testing: Quick testing of core functionalities after build or deployment.

Structural (White-box) Testing:

• Coverage Testing: Analyzed code coverage by tests (statement, branch, path coverage) to identify gaps.

Depending on the project and its specifics, other types such as A/B testing in product analytics were also used. The main focus was on automating regression and integration testing to maintain high product quality throughout the lifecycle.