Testing Links

To establish a clear procedure for defining which links clients will use for testing and how frequently changes are deployed to ensure consistency and clarity in the development process. This SOP applies to all project managers, developers, and clients involved in the testing and deployment phases of a project at LowCode Agency.

Step by step

1. Defining Testing Links:

Consult with Developer: Ask the developer where clients should test their changes:
- Test Link: Clients should primarily use the "version-test" link, which represents the MAIN environment.
- Live Link: This link is used when the application is ready to go live.
- Own Branch: Applicable if the client's Bubble plan allows additional branches.
Rationale:
- Clients should always test on MAIN to ensure consistency and readiness for live deployment.
- Exceptions occur when developers need to work on MAIN and clients need to test simultaneously. In such cases, branches are created if the client's plan allows.
- If the client's plan does not support branches, testing times should be coordinated with the developer.

2. Deployment Schedule:

Frequency of Deployments: Generally, deploy changes daily at the end of the day (EOD).
Deployment Scenarios:
- HOTFIXES:
  - Deploy immediately after the fix is made.
  - Applies to minor changes that do not affect app functionality (e.g., button color, text changes).
- FIRST-TIME FEATURES AND IMPLEMENTATION/FIXES ON LIVE APPS:
  - Deploy after the feature passes QA and is integrated into MAIN.
  - If urgent, deploy immediately after QA.
  - If not urgent, deploy weekly on Wednesdays before midday to allow time for any necessary fixes.
- FIRST-TIME FEATURES (Non-live Apps):
  - Deploy weekly on mid-week days before midday, assuming the feature is complete.

3. Monitoring Changes:

Komodo Guide:
- Use Komodo to monitor if changes are pushed to the client's link.
- Ensure the client is aware of how to check for updates.

4. Deployment to Live:

Deploy to live only after the client confirms that the MAIN environment meets their requirements.

Responsibilities:

Project Managers: Ensure clients are testing on the appropriate links and coordinate deployment schedules.
Developers: Communicate with project managers about the status of tasks and the readiness of features for deployment.
Clients: Test features on the MAIN environment and provide feedback.

To keep in mind

Always keep the client informed about the testing and deployment schedule.

Ensure clear communication between developers and clients to avoid conflicts during testing phases.

Maintain a flexible approach to accommodate urgent fixes and feature deployments while adhering to the general deployment schedule.