There are a variety of ways you can establish a QA process in Apptimize. We've outlined the general approaches here so that you can pick the method that best suits your product and needs. Click the links to find out more!
- QA Console
- Preferred method for native mobile apps. Requires you a one-time installation of our QA Console library so that you can just shake your device to pull up a menu and switch between variants. (A console for web is currently in development.)
- Preview Variants
- Tool directly available on our dashboard that simulates your mobile variants without any additional programming needs. This method is ideal for smaller teams and for visual experiments.
- Programmatic APIs
- Flexible methods that allow programmers to quickly test in development builds of your mobile app and force specific variants.
- Targeting-based QA
- Launching your tests in a Staging dashboard to your testing team allows you to most closely simulate the experience of an end-user. This is currently our main recommendation for QA on web/server-side. You can adjust your targeting rules to ensure only users who fulfill the conditions you set are eligible for your tests.
Note: Unfortunately, the first 3 options are currently not available for web QA (they are mobile-only approaches). For now, you can QA your web variants via option 4 by creating your project in staging and adjusting allocations for your variants. Apologies for the inconvenience, but we are currently working on more elegant QA tools for web! Let us know if you have any specific requests or questions at firstname.lastname@example.org
If you're curious about our recommended QA Best Practices, check out our article here!