Testing your app: Best Practices and Strategies

As an app developer using Shoplazza, testing your app is critical to ensure that it meets the highest standards of quality and functionality. Similarly, it is highly important to create a staging environment when introducing new features to your users and make it accessible only after thorough testing. In this guide, we'll explore best practices and strategies for testing your app on Shoplazza.

Creating an App exclusively for testing and development

By setting up a dedicated testing environment, you can test your app's performance and functionality without affecting your live store. To ensure a smooth and effective app development process, it's recommended to create two separate apps - one for testing and one for production.

Here are the steps to create your testing app:

1. Create another app using your staging environment parameters, such as the App URL and redirect URL.
2. Use this app solely for testing purposes, and you don't have to fill out all the required listings as the testing app doesn't need to be published to the app store.
3. Install your app in a development store through the "App testing" page, where you can begin testing its functionality. If you don't have a development store, you can follow the guide to create one.
4. Once you've fully developed and tested your app, deploy the code to your production app environment, specifically to the production App URL.
5. If your app hasn't been published to the app store yet, submit your production app for review, and your production code will be used once your app is approved and published to the app store  .
6. If your app is already published, deploying the code to your production app environment will immediately affect your users.

By following these steps, you can ensure that your app is thoroughly tested before releasing it to the public, while minimizing the risk of errors and bugs affecting your users' experience.

Using a feature flag to separate your testing environment

In this method, you won't have to create two separate apps for testing. Instead, you have the option of using a feature flag to separate your testing environment. Here's what you need to know:

• If your app hasn't been published to the app store   yet, there's no need to worry about using a feature flag, since any changes you make won't affect your users.
• However, if your app is already published to the app store, any changes you make will immediately impact your users. In this case, it's best to use a feature flag to separate your testing environment.
• To set up a feature flag for a feature entrance, you can make it accessible only to internal developers. This way, your app can maintain a testing environment that's only accessible to the internal team.
• Once your feature flag is ready to be published, you can simply remove the feature flag and release the new feature to all users.

By using a feature flag, you can ensure that your testing environment is separate from the production environment, allowing for efficient and safe testing without impacting your users' experience.

Critical bugs that impact App functionality

• If your app has critical bugs that impact its functionality and it hasn't been published to the app store yet, then you have to submit it for review. Your App won't be published until the issues have been addressed.
• If your app has already been published to the store and is found to have critical bugs, it may be unpublished. This is because such bugs violate our app review rules. You can refer to these app review rules for more information.

By testing your app thoroughly and following the best practices, you can avoid such situations and ensure that your app is stable and ready for release.