This page provides troubleshooting help and answers to frequently asked questions about running tests with Firebase Test Lab. If you can't find what you're looking for or need additional help, join the #test-lab channel on Firebase Slack or contact Firebase support.
Frequently asked questions
Firebase Test Lab offers no-cost quotas for testing on devices and for using Cloud APIs. Note that the testing quota uses the standard Firebase pricing plan, while the Cloud API quotas do not.
Testing quota
The no-cost testing quota comes with the Firebase Spark plan (see pricing plans for full detail). This is measured in the number of devices used to run tests. If you've reached your testing quota, wait until the next day or upgrade to the Blaze plan (for more information, see Testing quota for the Blaze plan).
Keep in mind that the no-cost daily quotas for Firebase pricing plans are enforced per Firebase project, not per app or per user. If you haven't already, check to make sure you haven't exceeded the quota for your Firebase project (for example, if you ran tests on another app in your project).
Cloud Testing API quota
The Cloud Testing API comes with two quota limits: requests per day per project, and requests per every 100 seconds per project. You can monitor your usage in the Google Cloud Console.
Cloud Tool Results API quota
The Cloud Tool Results API comes with two quota limits: queries per day per project, and queries per every 100 seconds per project. You can monitor your usage in the Google Cloud Console.
Refer to Cloud API quotas for Test Lab for more information on API limits. If you've reached an API quota:
Submit a request for higher quotas by editing your quotas directly in the Google Cloud Console (note that most limits are set to maximum by default), or
Request higher API quotas by filling out a request form in the Google Cloud Console or by contacting Firebase support.
From your backend, you can determine if traffic is coming from Firebase-hosted test devices by checking the source IP address against our IP ranges.
Test Lab does not work with VPC-SC, which blocks the copying of apps and other test artifacts between Test Lab's internal storage and users' results buckets. At the moment, a feature request has been filed to add VPC-SC support in a future release.
While some of these items are on our roadmap, we're currently unable to provide commitment to supporting these testing and app development platforms.