Test approach when we get the deployed software for testing:

Ever wondered why the QA team puts so much effort into testing even a single line of code or a minor change deployed to the QA environment?

Let’s take a moment to explore what we cover (and it’s a lot!) when a build is deployed for testing:

When a new build is deployed, I follow a structured and comprehensive approach to ensure the system is stable and ready for production. Here’s a step-by-step breakdown of my process:

1. Environment validation: Verify that the build is deployed correctly and doesn’t impact my access or login credentials.

2. Smoke Testing: Perform an initial smoke test to ensure the deployment was successful and the environment is stable.

3. Sanity Testing: Confirm that all user logins are functioning as expected and the system is behaving normally post-deployment.

4. Functional Testing: Test new functionality against the BRS, SRS, or Acceptance Criteria to ensure it’s working as intended.

5. Regression Testing: Conduct regression tests to ensure that existing features are unaffected by the new deployment.

6. Re-Testing: Validate that the system can handle multiple input scenarios and that input validations are functioning properly.

7. Load Testing: Simulate multiple user logins and test key functionalities to confirm the system can handle basic load levels.

8. Test Data Coverage: Use Equivalence Class Partitioning (ECP) and Boundary Value Analysis (BVA) to maximise test data coverage.

9. Bug Reporting: Log any identified bugs with detailed steps, logs, data points, and console outputs.

10. Bug triage meetings: Collaborate with the development team, business analysts, and product owners to prioritise bug fixes based on their impact and urgency.

11. Basic Security Testing: Test critical security functions, including invalid login attempts, password resets, multi-factor authentication, session management, and cookie tampering.

12. Load, Stress, and Endurance Testing: Simulate increasing user loads and stress the system to assess its performance under pressure and ensure it can handle long-term usage.

13. System Recovery Testing: Check that the system can recover from temporary failures or hangs, managing resources efficiently.

14. Cross-browser and OS Compatibility Testing: Test the application on multiple browsers and operating systems to ensure compatibility.

15. Test Traceability Metrics (TTM) and Test Requirement Metrics (TRM) Reports: Prepare detailed reports to track test coverage and ensure alignment with project requirements.

16. Documentation and Risk Management: Document the testing process, results, and any risks or mitigations taken. Maintain a log to track risks, action items, and approvals.

By following this comprehensive approach, I and my team ensure the system is thoroughly tested and prepared for production, with a focus on both functionality and performance. This methodology not only identifies bugs but also mitigates risks and improves overall product quality.