Test apps are child apps created from other, non-child apps. They are primarily used to clone apps that are already in Live mode in order to test new reviewable permissions and features without compromising the functionality of the cloned app.
Test apps are always in Development mode and inherit their parent app settings at the time that they are created. Once created, you can adjust a test app's settings to suit your testing needs.
An app user will be assigned the same app-scoped ID for your production and associated test apps.
Test apps inherit the Administrators and Testers from their parents. As with non-test apps, Testers can log into test apps but cannot see or edit app settings. Administrators have full control over the test app's settings, including the ability to add and remove people from roles.
People who have been added as Administrators to test apps (instead of inherited from their parents) can only perform admin actions on those test apps.
To create a test app:
You can now adjust your test app's settings and products and test new features and permissions without affecting the app from which it was cloned.
Testing a test app is just like testing any other app; update any SDK configurations that rely on your app ID and app secret with the test app's corresponding values and grant the test app relevant permissions using any user who has a role on the app itself, or a role on a business that has claimed the parent app.
You can remove test apps like you would any Facebook app.
Note: If you remove a parent app, all of its test apps will also be removed.
No. We suggest creating new test apps and migrating your development teams to use these new test apps for development, testing, QA, and staging purposes.
No. You will need to change settings in each test app manually or create a new test app to reflect the new settings.
No. You will need to update your production app's settings manually.