Features

Testing your app is an important part of the app building process to ensure everything works as expected before being accessed by your users. Testing your app offers the following features:

1. See how the app will look and feel for users before publishing.
2. Allow time to find and correct any mistakes before the app is live.

Testing Your App Security

Note: All apps should be tested after they are built and before being published as well as before any changes that have been made have been published and are live.

1. After making changes to your app in Fliplet Studio and before publishing your changes to the live app:
   1. Test the app in Preview Mode. Make sure that you test your app in all of the different device previews. When testing your app, if you click on the “enable security” button in the bottom right of the screen in preview mode. This ensures you are testing your app with any security rules you have set, in action, and applied. Use the reset preview button, to clear any logins to the app or settings you have applied during the testing and start as a fresh user testing the app.
   2. Test the app in Fliplet Viewer on iOS and Android. If the changes affect security or the initial screens it is recommended you delete the app in the Fliplet Viewer and download the app again, otherwise, you may not have access to the security or initial screens.
      
      
2. If the changes are OK publish the app in line with the following criteria:
   1. Notify your colleagues involved in the project that you are going to publish an update and ask them to review it once it is live.
   2. Only publish when you have time to review the update immediately.
      
      
3. Review the update in the Mobile and Web app:
   1. On all mobile platforms – iOS and Android.
   2. On all web browsers that your users could use: e.g. Chrome or IE.
      
      
4. Publish with plenty of time to undo the change if there are problems. 
5. If your checks pass ask your colleagues if they have successfully received the update.

Testing Changes On Different Devices And Browsers

For any apps that will be used on web, we recommend that for all changes or updates to your app testing is carried out on different devices and all supported browsers: e.g, Microsoft Edge, Firefox, and Chrome. We also recommend testing on Android and iOS to make sure that any changes are reflected and working correctly.

Be sure to test changes such as:

1. New features
2. New or removal of screens
3. Altering links or key screens
4. Modifying security rules
5. Modify data structures

The following changes to your app will go live immediately:

1. Adding or removing records to a data source without modifying the data source structure.
2. Data source changes. Most components retrieve data source updates without requiring the app to be published.
3. Components that retrieve data from an external data source, such as RSS or login components.

Related Articles