Bubble Devs | QA Best Practices

Best Practices for Deploying and Testing APPS

Purpose:
To define the standard process for developer testing in software projects, ensuring production-readiness and clear responsibilities for each environment.

• Dev should test features in both test and live environments to verify proper functionality and production readiness.

• Document deployment and testing practices as part of the project's best practices, and ensure they are communicated to all team members and clients.

• Developers perform testing on their assigned branch or on the main branch, depending on workflow and the nature of issues being addressed.

• Dev typically tests on a dedicated QA/Test branch, while final client testing occurs on the live environment once QA approves.

• Always ensure the live environment is tested at relevant stages to avoid outstanding issues surfacing only at project close or delivery.

• Schedule a kickoff call at the start of each project with PM, Devs, and QA to ensure all credentials and requirements are available before development begins.

• Maintain transparent documentation for all testing responsibilities and processes, updating them as workflows evolve.

Responsibilities:

• Developers: Test changes in their environment/branch before merging.

• Test both on the QA branch and on the live environment as needed.

• Project Manager: Facilitate scheduling, documentation, and communication of responsibilities.

• Client: Participate in testing on live after QA sign-off.

Review and Improvement:

• Periodically review this SOP and update as needed based on project retrospectives or changes in best practices.

This workflow ensures efficiency, prevents late-stage surprises, and supports delivery of production-ready software.