Kuota ini berlaku untuk level project, bukan level situs. Batasan ini dibagi untuk
semua API (termasuk uji instrumentasi, uji Robo, dan Game Loop
tes) dan matriks uji. Saat menjalankan pengujian, Anda dapat memeriksa runtime-nya (yaitu,
waktu yang dibutuhkan untuk menjalankan pengujian) pada Hasil eksekusi uji dan
matriks uji di Firebase console. Saat menggunakan Streaming Perangkat Android, Anda
dapat memeriksa penggunaan project di Android Studio atau
Google Cloud console. Runtime ditampilkan di samping setiap perangkat. Jika Anda menggunakan paket Blaze, waktu pengujian akan digunakan untuk penagihan.
Kuota
Kuota pengujian
Kuota pengujian Test Lab diukur dengan
jumlah pengujian yang dijalankan per hari:
Paket Spark (gratis): Batas resource tercantum
untuk maksimum 15 total pengujian per hari:
10 pengujian per hari di perangkat virtual
5 pengujian per hari di perangkat fisik
Paket Blaze: Tidak semua project dalam paket Blaze memiliki kuota yang sama. Jika
penggunaan Google Cloud Anda meningkat seiring waktu, kuota Anda mungkin
meningkat. Jika Anda memperkirakan peningkatan penggunaan yang akan datang cukup besar, Anda dapat
secara proaktif meminta penyesuaian kuota.
Penagihan dihitung berdasarkan menit yang dihabiskan untuk menjalankan pengujian. Paket Blaze
dimulai dengan batas waktu gratis yang mirip dengan batas resource yang ditawarkan
oleh paket Spark:
30 menit waktu pengujian per hari di perangkat fisik
60 menit waktu pengujian per hari di perangkat virtual
Setiap penggunaan yang melebihi batas ini akan ditagih sesuai dengan tarif per jam berikut:
$5 per jam untuk setiap perangkat fisik
$1 per jam untuk setiap perangkat virtual
Biaya dihitung per menit, yang dibulatkan ke menit terdekat. Misalnya, pengujian 22 detik ditagih satu menit, sementara pengujian 75 detik ditagih dua menit. Anda hanya dikenai biaya untuk
waktu yang dihabiskan untuk menjalankan pengujian (waktu yang diperlukan untuk menginstal aplikasi
dan mengumpulkan hasil pengujian tidak akan dikenai biaya).
Paket Spark (gratis): 30 menit tanpa biaya per project, per bulan
Paket Blaze: 30 menit tanpa biaya per project, per bulan, 15 sen untuk setiap menit tambahan
Tidak semua project dalam paket Blaze memiliki kuota yang sama. Jika penggunaan
Google Cloud console meningkat seiring waktu, kuota Anda mungkin
meningkat. Jika Anda memperkirakan peningkatan penggunaan yang akan datang cukup besar, Anda dapat
secara proaktif meminta penyesuaian kuota.
Menambah kuota
Jika telah mencapai kuota pengujian paket Blaze atau Cloud API, Anda dapat meminta
batas yang lebih tinggi dengan melakukan salah satu tindakan berikut:
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-29 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)."]]
