Managing a live store comes with its own set of challenges, particularly concerning security, stability, and performance. Making changes, such as installing new apps, can feel risky if their potential impact isn't well understood. However, by following established best practices, you can minimize risks and maintain smooth operations, protecting your store's stability and conversion rates.

Combining manual testing in development workspaces with A/B testing is a highly effective strategy. These steps allow you to identify and address potential issues before implementing changes for all users.

1. Install the app in a development workspace.
2. Link your local files to the development workspace with VTEX IO.
3. Access the store via the development workspace URL: {developmentWorkspaceName}--{accountName}.myvtex.com.
4. Navigate the store and perform manual tests to ensure the app behaves as expected. Look for any functionality issues or unintended side effects.
5. Visit the master workspace ({accountName}.myvtex.com) to identify any unexpected changes introduced by the app.
6. If all tests pass, install the app in a production workspace;

Set up an A/B test between the master workspace and the production workspace. During configuration, manually set traffic distribution for each workspace, directing a small percentage of users to the Production workspace.

Avoid relying on automatic traffic segmentation, which splits traffic 50/50, as it exposes a larger audience to potential issues.

1. If your changes involve a new major version of the Store Theme, refer to the Migrating CMS settings after a major theme update guide to avoid losing Admin page template settings.
2. Once validated, promote the production workspace to master, making the new configurations public for all your users.