Your company depends on the launch of high quality apps. To achieve this level, you must test your apps on a variety of devices. Pre-release reports use automated tests on real devices that can identify design issues, provide diagnostics on locks, discover security vulnerabilities, and much more. Then, you can run custom tests in Firebase Test Lab and use bug and ANR reports to look for more hidden problems.

Why it works


You must identify the problems of your app to ensure the best possible quality at the time of its launch. If you can correct the errors quickly, you can prevent the so unwanted negative reviews (especially if you respond to users to inform them that their problem has been corrected). You can also improve the experience of new users, which will impact0

Identify the problems of your app to ensure the best possible quality at the time of launch. If you correct errors quickly, you can revert negative reviews (especially if you respond to users to inform them that the problem was corrected). You can also improve the experience of new users, which will positively impact ratings and reviews.

Functions

  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Pre-launch reports : Show a summary of the problems presented by the Alpha and Beta test apps, which are automatically tested to verify device compatibility, display problems and security vulnerabilities on a wide variety of devices in Firebase Test Lab. & nbsp;
  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Custom tests with Firebase & nbsp; Test & nbsp; Lab : Detect defects in the programming process, by running tests with scripts in your app, with the custom tests of Firebase Test Lab. & nbsp;
  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Bug reports and "the app is not responding" (ANR) : If your app fails or stops responding, and the user wants to send their comments, Google Play will collect the important information and show it to you in the Google Play Developer Console. If you review these bug and ANR reports, you can identify the problems in your app and update it to fix them. & nbsp;
  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Firebase crash report : Get detailed reports of your app errors. Errors are grouped into clusters with similar record groups and classified by severity of impact on your users. In addition to receiving automatic reports, you can register custom events to detect the steps that lead to blocking. & nbsp;
  • Recommendations

  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Compare compilations to track progress . As part of the pre-release report, the Bugs tab shows a chart with the support of your APKs compared to previous compilations. Each bar of the report represents a compilation of your Alpha or Beta APK that was recently tested, along with the number of successful and failed launches that were detected during the test. & nbsp;
  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Check how your app works on different versions of Android . With the pre-launch report, near the bottom half of the Bug tab of your app, you can see individual reportsthat show the test device and the Android version with a red icon that indicates if your app had problems during the test. & nbsp;
  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Discover design problems . The screenshots in the summary of each test allow you to see the appearance of your app on test devices with different versions of Android, languages ​​and screen resolutions. & nbsp;
  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Upload another Alpha or Beta test . It is possible for a test to show "Devices not available" in your results, even if your APK is compatible with those devices. Upload another Alpha or Beta APK to make sure the app works with all devices. & nbsp;
  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Identify security vulnerabilities . Known security vulnerabilities are marked so you can take action and ensure that your app is safe for users. The report even looks for problems in third-party libraries. The names and descriptions of the security vulnerabilities that are in your APK are included in the report prior to the launch of each test. & nbsp;
  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Use a one-click access button . If your app includes an access screen that requires the entry of credentials, it is possible that less results will be shown in the test, since the process can not pass these screens. To expand the test coverage, publish an Alpha or Beta app with a one-click "access" button that allows the process to continue with the test. & nbsp;
  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Remove the location requirements . It is possible that your app depends on geolocation and that the location of the test devices does not meet this requirement. In this case, publish an Alpha or Beta APK that removes the location requirements, especially if the content of your app has content restrictions depending on the country. & nbsp;
  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Incorporate data you want to include in the tests . If you want to run tests on an app with preloaded data, publish an Alpha or Beta version with the multimedia files incorporated in the APK. & nbsp;
  • & nbsp; & nbsp;
  • & nbsp; & nbsp; Disables Google licensing services & nbsp; Play . To make sure that your app correctly identifies users on test devices, create an Alpha or Beta version with the Google Play license services disabled. Otherwise, you will receive less results in the tests. & nbsp;