Method

Description

Limitations

Testlio Build Upload API

The Testlio Build Upload API allows you to upload builds and related metadata
directly to the Testlio Platform.

The integration requires minimal effort and is compatible with most CI/CD tools.

This is the most secure and the preferred way of sharing build information with Testlio.

Testing push notifications on iOS and production payments on iOS or Android requires a separate build upload to TestFlight/Google Play.

Manual build upload to Testlio Platform

You can access the Testlio Platform to upload builds manually and use the same functions that the Testlio Build Upload API provides.

This option is suitable when you have an ad-hoc need to upload a build.

Testing push notifications on iOS and production payments on iOS or Android requires a separate build upload to TestFlight/Google Play.

3rd-party build-sharing tools with allow-listed tester accounts

Build-sharing tools like TestFlight and Google Play provide an option to share the builds only to a specified list of tester accounts.

This method is suitable when the Testlio Build Upload API is not supported and the build contains sensitive information or free access to otherwise paid (subscription) services.

Your team and the Testlio team will need to manually maintain the list of allowed tester accounts.

This results in potential delays in turnaround time and a reduced ability to quickly expand coverage.

3rd-party build-sharing tools with a publicly accessible link to the build

Build-sharing tools like TestFlight and Google Play allow build sharing via a publicly accessible link/sign-up method.

This method is suitable when the Testlio Build Upload API is not supported and the build does not contain sensitive information or free access to otherwise paid (subscription) services.

IMPORTANT

As in this case the builds are accessible to anyone in the world with the link, you need to acknowledge and understand that 3rd parties might gain access to the link.

If the build contains access to features that allow free use of the product or are sensitive in nature, you need to either use alternative build sharing methods or add an additional layer of security or limitations in place to avoid misuse of the features (such as feature-flagging or allow-listing to match only Testlio freelancers).

You must ensure additional security measures are implemented before sharing the link. This is critical for the safety of information and to avoid potential security incidents. Testlio does not control the flow of information when links are shared using publicly accessible means, and so Testlio will not be responsible unless the security incident is directly associated with Testlio breaching its security obligations.