Robo 테스트: 앱 인터페이스를 분석한 후 사용자 활동을 시뮬레이션하여 자동으로 탐색하는 테스트입니다.
게임 루프 테스트: 게임 앱에서 '데모 모드'를 사용하여 플레이어 동작을 시뮬레이션하는 테스트입니다.
시작하기 전에
Firebase 프로젝트가 사용한 만큼만 지불하는 Blaze 요금제를 사용하고 있어야 합니다. 즉, 프로젝트가 Cloud Billing 계정에 연결되어 있어야 합니다. Firebase Console에서 Blaze 요금제로 업그레이드할 수 있습니다. Cloud Billing 계정을 연결하려면 프로젝트의 소유자 또는 편집자여야 합니다.
Firebase Console의 Test Lab 페이지에서 첫 번째 테스트 실행 > Android 게임 루프 실행을 클릭합니다.
앱 업로드 섹션에서 찾아보기를 클릭한 다음 앱의 APK 파일을 선택합니다. 아직 앱의 APK 파일을 생성하지 않았다면 APK 파일을 생성합니다.
(선택사항) Firebase Console에서 테스트 매트릭스를 식별하고 찾는 데 도움이 되도록 테스트 매트릭스 라벨(선택사항) 필드에 라벨 이름을 입력하여 테스트 매트릭스에 라벨을 추가할 수 있습니다.
(선택사항) 한 번에 여러 루프 또는 시나리오를 실행하거나 실행할 특정 루프를 선택하려면 시나리오 필드에 루프 번호를 입력합니다.
예를 들어 '1-3, 5'를 입력하면 Test Lab에서 루프 1, 2, 3, 5를 실행합니다.
시나리오 필드에 아무것도 입력하지 않으면 기본적으로 Test Lab은 루프 1만 실행합니다.
기기 섹션에서 앱을 테스트할 하나 이상의 실제 기기를 선택한 다음 테스트 시작을 클릭합니다.
3단계: 테스트 결과 검토
테스트가 시작되면 자동으로 테스트 결과 페이지로 리디렉션됩니다.
선택한 구성의 가짓수 및 테스트에 설정한 제한 시간에 따라 테스트 완료까지 몇 분 정도
걸릴 수 있습니다. 테스트가 완료된 후 테스트 결과를 검토할 수 있습니다. 테스트 결과를 해석하는 방법은 Firebase Test Lab 결과 분석을 참조하세요.
[null,null,["최종 업데이트: 2025-08-16(UTC)"],[],[],null,["\u003cbr /\u003e\n\nFirebase Test Lab provides cloud-based infrastructure for testing\nAndroid apps. This document describes how to get started with Test Lab using the\nFirebase console.\n\nTest Lab lets you run the following types of tests:\n\n- [Instrumentation test](/docs/test-lab/android/instrumentation-test):\n A test you write that allows you to drive the UI of your app with the actions\n you specify. An instrumentation test can also make explicit assertions about\n the state of your app to verify correct functionality using\n [AndroidJUnitRunnerAPIs](https://developer.android.com/reference/android/support/test/runner/AndroidJUnitRunner). Test Lab supports\n [Espresso](https://developer.android.com/training/testing/espresso)\n and\n [UI Automator](https://developer.android.com/training/testing/other-components/ui-automator) instrumentation test frameworks.\n\n- [Robo test](/docs/test-lab/android/robo-ux-test):\n A test that analyzes your app's interface and then explores it automatically\n by simulating user activities.\n\n- [Game loop test](/docs/test-lab/android/game-loop): A test\n that uses a \"demo mode\" to simulate player actions in game apps.\n\nBefore you begin\n\nYour Firebase project must be on the [pay-as-you-go Blaze pricing plan](/pricing), which means that\nyour project is linked to a Cloud Billing account. You can\n[upgrade to the Blaze pricing plan](//console.firebase.google.com/project/_/overview?purchaseBillingPlan=metered)\nin the Firebase console. You need to be an Owner or Editor for your project\nto link a Cloud Billing account.\n\nStep 1. Create a Firebase project\n\nIf you haven't yet, go to the [Firebase console](https://console.firebase.google.com/)\nand create a new Firebase project.\n| **Note:** If you're working on a shared Firebase project, you'll need to have ownership or edit permissions for the project.\n\nStep 2. Run a test \n\nInstrumentation test**Note:** If you want to run an instrumentation test with [Android Test Orchestrator](https://developer.android.com/training/testing/junit-runner.html#using-android-test-orchestrator), see [Enable Orchestrator](/docs/test-lab/android/instrumentation-test#orchestrator).\n\n1. On the [Firebase console](https://g.co/firebase) navigation bar,\n click **Test Lab** , and then click **Get Started -\\\u003e Run an Instrumentation\n test**.\n\n2. Click **Browse** , and then browse to your app APK or AAB and test APK or\n AAB before clicking **Continue**.\n\n3. Define your test matrix by selecting which devices, Android API levels,\n screen orientations and locales you want to test your app against. You can\n select only those device and Android API level combinations that you want\n to target for testing.\n\n4. (Optional) Click **Show advanced options** to change the Test timeout\n that determines the maximum duration of each test execution.\n\n5. (Optional) To help you identify and locate your test matrices in the\n Firebase console, you can add a label to your test matrix by entering a\n label name in the **Test matrix label (optional)** field.\n\n6. Click **Start *N* Tests**, where \"N\" is the number of valid test\n configurations from the test matrix that you define on this screen. Each\n pending test is shown with a blue clock icon while it is waiting to run,\n and that icon changes to a green check icon when the test has completed.\n\n7. After each test has run, click the device listed in the Test Execution\n column to see test results, including test cases, logs, screenshots and\n videos.\n\nRobo test\n\n1. On the [Firebase console](https://g.co/firebase) navigation bar,\n click **Test Lab** , and then click **Get Started -\\\u003e Run a Robo test**.\n\n2. Click **Browse** , browse to your app APK, and then click **Continue**.\n\n3. Define your test matrix by selecting which devices, Android API levels,\n screen orientations and locales you want to test your app against.\n\n4. (Optional) Click **Show advanced options** to change the following options:\n\n - Test timeout determines the maximum duration of each test execution.\n - Test account credentials are usedis used to provide credentials for a test account.\n\n | **Caution:** Never use this option with real user accounts.\n - Additional fields are used to provide text input for other text fields in your app.\n\n | **Note:** To learn more about Test account credentials and additional fields, see [Test account sign-in and predefined text](/docs/test-lab/robo-ux-test#test_account_sign-in_and_predefined_text_input).\n5. (Optional) To help you identify and locate your test matrices in the\n Firebase console, you can add a label to your test matrix by entering\n a label name in the **Test matrix label (optional)** field.\n\n6. Click **Start *N* Tests**, where \"N\" is the number of valid test\n configurations from the test matrix that you define on this screen. Each\n pending test is shown with a blue clock icon while it is waiting to run,\n and that icon changes to a green check when the test has completed.\n\n7. After each test finishes running, click the device listed in the Test\n Execution column to see test results, including test cases, logs,\n screenshots and videos.\n\nIf you want to create a script to guide the Robo test, see\n[Record a Robo script using Test Lab in Android Studio](/docs/test-lab/android/run-robo-scripts#record-android-studio).\n\nGame Loop test\n\n1. On the Test Lab page of the [Firebase console](https://console.firebase.google.com/project/_/%0Atestlab), click **Run Your First Test \\\u003e Run an Android Game Loop**.\n\n2. In the **Upload App** section, click **Browse** , then select your app's\n APK file (if you haven't already, [generate an APK file](https://firebase.google.com/docs/test-lab/android/game-loop#run-testlab) for your app).\n\n3. (Optional) To help you identify and locate your test matrices in the\n Firebase console, you can add a label to your test matrix by entering\n a label name in the **Test matrix label (optional)** field.\n\n4. (Optional) If you want to run multiple loops or scenarios at a time, or\n select specific loops to run, enter the loop numbers in the\n **Scenarios** field.\n\n For example, when you enter \"1-3, 5\", Test Lab runs loops 1, 2, 3, and 5.\n By default (if you don't enter anything in the **Scenarios** field),\n Test Lab only runs loop 1.\n5. In the **Devices** section, select one or more physical devices you\n want to test your app on, then click **Start Tests**.\n\nStep 3. Investigate your test results\n\nWhen the test starts, you're automatically redirected to the test results page.\nTests can take a number of minutes to run, depending on the number of different\nconfigurations you have selected and the test timeout duration set for your\ntests. After your tests have run, you can review test results. See\n[Analyzing Firebase Test Lab Results](/docs/test-lab/android/analyzing-results) to learn more\nabout how to interpret the test results.\n| **Note:** For all test types, any uncaught exception will cause a test failure."]]
