Stay organized with collections
Save and categorize content based on your preferences.
Firebase Test Lab and Android Device
Streaming
provide a Cloud API quota and a testing quota, which is included in the standard
Spark and Blaze pricing
plans. These quotas are based on your project's usage of the testing
resource, device resource or Cloud
API.
These quotas are applied project-level, not site-level. These limits are shared
across all APIs (including instrumentation tests, Robo tests, and Game Loop
tests) and test matrixes. When you run a test, you can check its run time (i.e.,
the time it takes the test to run) under Test execution and test matrix
results in the Firebase console. When using Android Device Streaming, you
can check your project's usage in either Android Studio or
Google Cloud console. Run times are displayed next to each device. If you're in
the Blaze plan, the test run times are used for billing.
Quotas
Testing quota
Test Lab's testing quota is measured by the
number of test runs per day:
Spark plan (no-cost): The resource limits are
listed for up to 15 test runs per day in total:
10 test runs per day on virtual devices
5 test runs per day on physical devices
Blaze plan: Not all projects in the Blaze plan have the same quotas. If
your usage of Google Cloud increases over time, your quotas might increase
correspondingly. If you expect a sizable upcoming increase in usage, you can
proactively request quota adjustments.
Billing is calculated by the minutes spent running tests. The Blaze plan
begins with a no-cost time limit that's similar to the resource limit offered
by the Spark plan:
30 minutes of test time per day on physical devices
60 minutes of test time per day on virtual devices
Any usage above these limits is charged according to the following hourly
rates:
$5 per hour for each physical device
$1 per hour for each virtual device
Charges are calculated on a per-minute basis, rounded up to the nearest
minute. For example, a 22-second test is billed for one minute, while a
75-second test is billed for two minutes. You are charged only for the
time spent running tests (the time it takes to install your app
and collect test results will not be charged).
(no cost) Spark plan: 30 no cost minutes per project, per month
Blaze plan: 30 no cost minutes per project, per month, 15 cents for each additional minute
Not all projects in the Blaze plan have the same quotas. If your usage of
Google Cloud console increases over time, your quotas might increase
correspondingly. If you expect a sizable upcoming increase in usage, you can
proactively request quota adjustments.
Increase quotas
If you've reached a Cloud API or Blaze plan testing quota, you can request a
higher limit by doing one of the following:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["\u003cbr /\u003e\n\nFirebase Test Lab and [Android Device\nStreaming](https://developer.android.com/studio/run/android-device-streaming)\nprovide a Cloud API quota and a testing quota, which is included in the standard\nSpark and Blaze pricing\nplans. These quotas are based on your project's usage of the [testing\nresource](#testing-quota), [device resource](#device-streaming) or [Cloud\nAPI](#cloud-api-quota).\n\nThese quotas are applied project-level, not site-level. These limits are shared\nacross all APIs (including instrumentation tests, Robo tests, and Game Loop\ntests) and test matrixes. When you run a test, you can check its run time (i.e.,\nthe time it takes the test to run) under **Test execution and test matrix\nresults** in the Firebase console. When using Android Device Streaming, you\ncan check your project's usage in either Android Studio or\nGoogle Cloud console. Run times are displayed next to each device. If you're in\nthe Blaze plan, the test run times are used for billing.\n| When your project is on the Blaze pricing plan, [**set up budget alerts**](/docs/projects/billing/avoid-surprise-bills#set-up-budget-alert-emails) using the console. You can use the [Blaze plan calculator](/pricing#blaze-calculator) to estimate your monthly costs.\n|\n| Be aware that **budget alerts do *not* cap your usage or\n| charges** --- they are *alerts* about your costs so that you can\n| take action, if needed. For example, you might consider\n| [using\n| budget notifications to programmatically disable Cloud Billing on a\n| project](https://cloud.google.com/billing/docs/how-to/disable-billing-with-notifications).\n\n**Quotas**\n\nTesting quota\n\nTest Lab's testing quota is measured by the\nnumber of test runs per day:\n\n- **Spark plan (no-cost)**: The resource limits are\n listed for up to 15 test runs per day in total:\n\n - 10 test runs per day on virtual devices\n\n - 5 test runs per day on physical devices\n\n- **Blaze plan** : Not all projects in the Blaze plan have the same quotas. If\n your usage of Google Cloud increases over time, your quotas might increase\n correspondingly. If you expect a sizable upcoming increase in usage, you can\n proactively request [quota adjustments](#increase-cloud-quotas).\n\n Billing is calculated by the minutes spent running tests. The Blaze plan\n begins with a no-cost time limit that's similar to the resource limit offered\n by the Spark plan:\n - 30 minutes of test time per day on physical devices\n\n - 60 minutes of test time per day on virtual devices\n\n Any usage above these limits is charged according to the following hourly\n rates:\n - $5 per hour for each physical device\n\n - $1 per hour for each virtual device\n\nCharges are calculated on a per-minute basis, rounded up to the nearest\nminute. For example, a 22-second test is billed for one minute, while a\n75-second test is billed for two minutes. You are charged only for the\ntime spent running tests (the time it takes to install your app\nand collect test results will not be charged).\n\nYou can monitor your testing quota usage in the\n[Google Cloud console](https://console.cloud.google.com/apis/api/testing.googleapis.com/quotas).\n\nCloud API quotas\n\nThe Testing and Tool Results APIs come with two API limits: requests per day per\nproject, and requests per minute per project.\n\n- Cloud Testing API limit (including calls for Android Device Streaming):\n\n - 10,000,000 calls per day\n - 120,000 calls per 1-minute interval\n\n You can monitor your usage of this API in the\n [Google Cloud console](https://console.cloud.google.com/apis/api/testing.googleapis.com/quotas).\n- Cloud Tool Results API limit:\n\n - 200,000 calls per day\n - 2,400 calls per 1-minute interval\n\n You can monitor your usage of this API in the\n [Google Cloud console](https://console.cloud.google.com/apis/api/toolresults.googleapis.com/quotas).\n\nAndroid Device Streaming quotas\n\n- **(no cost) Spark plan**: 30 no cost minutes per project, per month\n- **Blaze plan**: 30 no cost minutes per project, per month, 15 cents for each additional minute\n\nNot all projects in the Blaze plan have the same quotas. If your usage of\nGoogle Cloud console increases over time, your quotas might increase\ncorrespondingly. If you expect a sizable upcoming increase in usage, you can\nproactively request [quota adjustments](/docs/test-lab/usage-quotas-pricing#increase-cloud-quotas).\n\nIncrease quotas\n\nIf you've reached a Cloud API or Blaze plan testing quota, you can request a\nhigher limit by doing one of the following:\n\n- [Submitting an increase request](https://cloud.google.com/docs/quota#requesting_higher_quota)\n directly in the Google Cloud console.\n\n- Contacting [Firebase support](https://support.google.com/firebase/contact/support)."]]