imjasonh/gcloud-help
1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 02:25:19 +00:00
Code Activity

gcloud: Tue Mar 1 04:29:52 UTC 2022

Browse source
This commit is contained in:
Automated 2022-03-01 04:29:52 +00:00
parent aab53307a8
commit 1456dab6c7
9791 changed files with 814712 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

75
gcloud/firebase/test/android/help Normal file
View file

@ -0,0 +1,75 @@
NAME
gcloud firebase test android - command group for Android application
testing
SYNOPSIS
gcloud firebase test android GROUP | COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Explore physical and virtual Android models, Android OS versions, and
Android locales which are available as test targets. Also run tests against
your Android app on these devices, monitor your test progress, and view
detailed test results in the Firebase console.
EXAMPLES
To see a list of available Android devices, their form factors, and
supported Android OS versions, run:
$ gcloud firebase test android models list
To view more detailed information about a specific Android model, run:
$ gcloud firebase test android models describe MODEL_ID
To view details about available Android OS versions, such as their code
names and release dates, run:
$ gcloud firebase test android versions list
To view information about a specific Android OS version, run:
$ gcloud firebase test android versions describe VERSION_ID
To view the list of available Android locales which can be used for testing
internationalized applications, run:
$ gcloud firebase test android locales list
To view information about a specific locale, run:
$ gcloud firebase test android locales describe LOCALE
To view all options available for running Android tests, run:
$ gcloud firebase test android run --help
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
GROUPS
GROUP is one of the following:
locales
Explore Android locales available for testing.
models
Explore Android models available in the Test Environment catalog.
versions
Explore Android versions available for testing.
COMMANDS
COMMAND is one of the following:
run
Invoke a test in Firebase Test Lab for Android and view test results.
NOTES
These variants are also available:
$ gcloud alpha firebase test android
$ gcloud beta firebase test android

34
gcloud/firebase/test/android/locales/describe Normal file
View file

@ -0,0 +1,34 @@
NAME
gcloud firebase test android locales describe - describe an Android locale
SYNOPSIS
gcloud firebase test android locales describe LOCALE [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Describe an Android locale.
EXAMPLES
To see the attributes of the Android locale 'my-locale', run:
$ gcloud firebase test android locales describe my-locale
POSITIONAL ARGUMENTS
LOCALE
The locale to describe, found using $ gcloud firebase test android
locales list.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test android locales describe
$ gcloud beta firebase test android locales describe

41
gcloud/firebase/test/android/locales/help Normal file
View file

@ -0,0 +1,41 @@
NAME
gcloud firebase test android locales - explore Android locales available
for testing
SYNOPSIS
gcloud firebase test android locales COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Explore Android locales available for testing.
EXAMPLES
To list all available Android locales which can be used for testing
international applications, run:
$ gcloud firebase test android locales list
To view information about a specific locale, run:
$ gcloud firebase test android locales describe LOCALE
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
describe
Describe an Android locale.
list
List all Android locales available for testing internationalized apps.
NOTES
These variants are also available:
$ gcloud alpha firebase test android locales
$ gcloud beta firebase test android locales

63
gcloud/firebase/test/android/locales/list Normal file
View file

@ -0,0 +1,63 @@
NAME
gcloud firebase test android locales list - list all Android locales
available for testing internationalized apps
SYNOPSIS
gcloud firebase test android locales list [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List all Android locales available for testing internationalized apps.
EXAMPLES
To list all available locales which can be used for testing
internationalized Android applications, run:
$ gcloud firebase test android locales list
To filter the locales to see only Spanish-speaking regions, run:
$ gcloud firebase test android locales list --filter=Spanish
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test android locales list
$ gcloud beta firebase test android locales list

35
gcloud/firebase/test/android/models/describe Normal file
View file

@ -0,0 +1,35 @@
NAME
gcloud firebase test android models describe - describe an Android model
SYNOPSIS
gcloud firebase test android models describe MODEL_ID
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Describe an Android model.
EXAMPLES
To see the attributes of the android model 'my-model', run:
$ gcloud firebase test android models describe my-model
POSITIONAL ARGUMENTS
MODEL_ID
ID of the model to describe, found using $ gcloud firebase test android
models list.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test android models describe
$ gcloud beta firebase test android models describe

41
gcloud/firebase/test/android/models/help Normal file
View file

@ -0,0 +1,41 @@
NAME
gcloud firebase test android models - explore Android models available in
the Test Environment catalog
SYNOPSIS
gcloud firebase test android models COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Explore Android models available in the Test Environment catalog.
EXAMPLES
To list all Android models available for running tests, along with their
basic characteristics and supported Android OS versions, run:
$ gcloud firebase test android models list
To view more detailed information about a specific Android model, run:
$ gcloud firebase test android models describe MODEL_ID
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
describe
Describe an Android model.
list
List all Android models available for testing.
NOTES
These variants are also available:
$ gcloud alpha firebase test android models
$ gcloud beta firebase test android models

66
gcloud/firebase/test/android/models/list Normal file
View file

@ -0,0 +1,66 @@
NAME
gcloud firebase test android models list - list all Android models
available for testing
SYNOPSIS
gcloud firebase test android models list [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List all Android models available for testing.
EXAMPLES
To list all models which are available for testing, run:
$ gcloud firebase test android models list
To list all models made by Samsung, run:
$ gcloud firebase test android models list --filter=Samsung
To list all virtual device models, run:
$ gcloud firebase test android models list --filter=virtual
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test android models list
$ gcloud beta firebase test android models list

478
gcloud/firebase/test/android/run Normal file
View file

@ -0,0 +1,478 @@
NAME
gcloud firebase test android run - invoke a test in Firebase Test Lab for
Android and view test results
SYNOPSIS
gcloud firebase test android run [ARGSPEC] [--app=APP]
[--device=DIMENSION=VALUE,[...]] [--test=TEST] [--timeout=TIMEOUT]
[--type=TYPE] [--additional-apks=APK,[APK,...]]
[--app-package=APP_PACKAGE] [--async] [--auto-google-login]
[--directories-to-pull=[DIR_TO_PULL,...]]
[--environment-variables=[KEY=VALUE,...]]
[--network-profile=PROFILE_ID] [--num-flaky-test-attempts=int]
[--obb-files=OBB_FILE,[OBB_FILE]]
[--other-files=DEVICE_PATH=FILE_PATH,[...]] [--performance-metrics]
[--record-video] [--results-bucket=RESULTS_BUCKET]
[--results-dir=RESULTS_DIR]
[--results-history-name=RESULTS_HISTORY_NAME]
[--scenario-labels=LABEL,[LABEL,...]]
[--scenario-numbers=int,[int,...]] [--test-package=TEST_PACKAGE]
[--test-runner-class=TEST_RUNNER_CLASS]
[--test-targets=TEST_TARGET,[TEST_TARGET,...]] [--use-orchestrator]
[--robo-directives=[TYPE:RESOURCE_NAME=INPUT,...]]
[--robo-script=ROBO_SCRIPT]
[--device-ids=MODEL_ID,[MODEL_ID,...], -d MODEL_ID,[MODEL_ID,...]]
[--locales=LOCALE,[LOCALE,...], -l LOCALE,[LOCALE,...]]
[--orientations=ORIENTATION,[ORIENTATION],
-o ORIENTATION,[ORIENTATION]]
[--os-version-ids=OS_VERSION_ID,[...], -v OS_VERSION_ID,[...]]
[--filter=EXPRESSION] [--limit=LIMIT] [--page-size=PAGE_SIZE]
[--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud firebase test android run invokes and monitors tests in Firebase
Test Lab for Android.
Three main types of Android tests are currently supported:
▪ robo: runs a smart, automated exploration of the activities in your
Android app which records any installation failures or crashes and
builds an activity map with associated screenshots and video.
▪ instrumentation: runs automated unit or integration tests written
using a testing framework. Firebase Test Lab for Android currently
supports the Espresso and UI Automator 2.0 testing frameworks.
▪ game-loop: executes a special intent built into the game app (a "demo
mode") that simulates the actions of a real player. This test type can
include multiple game loops (also called "scenarios"), which can be
logically organized using scenario labels so that you can run related
loops together. Refer to
https://firebase.google.com/docs/test-lab/android/game-loop for more
information about how to build and run Game Loop tests.
The type of test to run can be specified with the --type flag, although the
type can often be inferred from other flags. Specifically, if the --test
flag is present, the test --type defaults to instrumentation. If --test is
not present, then --type defaults to robo.
All arguments for gcloud firebase test android run may be specified on the
command line and/or within an argument file. Run $ gcloud topic arg-files
for more information about argument files.
EXAMPLES
To invoke a robo test lasting 100 seconds against the default device
environment, run:
$ gcloud firebase test android run --app=APP_APK --timeout=100s
When specifying devices to test against, the preferred method is to use the
--device flag. For example, to invoke a robo test against a virtual,
generic MDPI Nexus device in landscape orientation, run:
$ gcloud firebase test android run --app=APP_APK \
--device=model=NexusLowRes,orientation=landscape
To invoke an instrumentation test against a physical Nexus 6 device
(MODEL_ID: shamu) which is running Android API level 21 in French, run:
$ gcloud firebase test android run --app=APP_APK --test=TEST_APK \
--device=model=shamu,version=21,locale=fr
To test against multiple devices, specify --device more than once:
$ gcloud firebase test android run --app=APP_APK --test=TEST_APK \
--device=model=Nexus4,version=19 \
--device=model=Nexus4,version=21 \
--device=model=NexusLowRes,version=25
To invoke a robo test on an Android App Bundle, pass the .aab file using
the --app flag.
$ gcloud firebase test android run --app=bundle.aab
You may also use the legacy dimension flags (deprecated) to specify which
devices to use. Firebase Test Lab will run tests against every possible
combination of the listed device dimensions. Note that some combinations of
device models and OS versions may not be valid or available in Test Lab.
Any unsupported combinations of dimensions in the test matrix will be
skipped.
For example, to execute a series of 5-minute robo tests against a very
comprehensive matrix of virtual and physical devices, OS versions, locales
and orientations, run:
$ gcloud firebase test android run --app=APP_APK --timeout=5m \
--device-ids=shamu,NexusLowRes,Nexus5,g3,zeroflte \
--os-version-ids=19,21,22,23,24,25 --locales=en_GB,es,fr,ru,zh \
--orientations=portrait,landscape
The above command will generate a test matrix with a total of 300 test
executions, but only the subset of executions with valid dimension
combinations will actually run your tests.
Controlling Results Storage
By default, Firebase Test Lab stores detailed test results for a limited
time in a Google Cloud Storage bucket provided for you at no charge. If you
wish to use a storage bucket that you control, or if you need to retain
detailed test results for a longer period, use the --results-bucket option.
See https://firebase.google.com/docs/test-lab/analyzing-results#detailed
for more information.
Detailed test result files are prefixed by default with a timestamp and a
random character string. If you require a predictable path where detailed
test results are stored within the results bucket (say, if you have a
Continuous Integration system which does custom post-processing of test
result artifacts), use the --results-dir option. Note that each test
invocation must have a unique storage location, so never reuse the same
value for --results-dir between different test runs. Possible strategies
could include using a UUID or sequence number for --results-dir.
For example, to run a robo test using a specific Google Cloud Storage
location to hold the raw test results, run:
$ gcloud firebase test android run --app=APP_APK \
--results-bucket=gs://my-bucket \
--results-dir=my/test/results/<unique-value>
To run an instrumentation test and specify a custom name under which the
history of your tests will be collected and displayed in the Firebase
console, run:
$ gcloud firebase test android run --app=APP_APK --test=TEST_APK \
--results-history-name='Excelsior App Test History'
Argument Files
All test arguments for a given test may alternatively be stored in an
argument group within a YAML-formatted argument file. The ARG_FILE may
contain one or more named argument groups, and argument groups may be
combined using the include: attribute (Run $ gcloud topic arg-files for
more information). The ARG_FILE can easily be shared with colleagues or
placed under source control to ensure consistent test executions.
To run a test using arguments loaded from an ARG_FILE named excelsior_args,
which contains an argument group named robo-args:, use the following
syntax:
$ gcloud firebase test android run path/to/excelsior_args:robo-args
POSITIONAL ARGUMENTS
[ARGSPEC]
An ARG_FILE:ARG_GROUP_NAME pair, where ARG_FILE is the path to a file
containing groups of test arguments in yaml format, and ARG_GROUP_NAME
is the particular yaml object holding a group of arg:value pairs to
use. Run $ gcloud topic arg-files for more information and examples.
COMMONLY USED FLAGS
--app=APP
The path to the application binary file. The path may be in the local
filesystem or in Google Cloud Storage using gs:// notation. Android App
Bundles are specified as .aab, all other files are assumed to be APKs.
--device=DIMENSION=VALUE,[...]
A list of DIMENSION=VALUE pairs which specify a target device to test
against. This flag may be repeated to specify multiple devices. The
four device dimensions are: model, version, locale, and orientation. If
any dimensions are omitted, they will use a default value. The default
value, and all possible values, for each dimension can be found with
the list command for that dimension, such as $ gcloud firebase test
android models list. --device is now the preferred way to specify test
devices and may not be used in conjunction with --devices-ids,
--os-version-ids, --locales, or --orientations. Omitting all of the
preceding dimension-related flags will run tests against a single
device using defaults for all four device dimensions.
Examples:
--device model=Nexus6
--device version=23,orientation=portrait
--device model=shamu,version=22,locale=zh_CN,orientation=default
--test=TEST
The path to the binary file containing instrumentation tests. The given
path may be in the local filesystem or in Google Cloud Storage using a
URL beginning with gs://.
--timeout=TIMEOUT
The max time this test execution can run before it is cancelled
(default: 15m). It does not include any time necessary to prepare and
clean up the target device. The maximum possible testing time is 45m on
physical devices and 60m on virtual devices. The TIMEOUT units can be
h, m, or s. If no unit is given, seconds are assumed. Examples:
◆ --timeout 1h is 1 hour
◆ --timeout 5m is 5 minutes
◆ --timeout 200s is 200 seconds
◆ --timeout 100 is 100 seconds
--type=TYPE
The type of test to run. TYPE must be one of: instrumentation, robo,
game-loop.
FLAGS
--additional-apks=APK,[APK,...]
A list of up to 100 additional APKs to install, in addition to those
being directly tested. The path may be in the local filesystem or in
Google Cloud Storage using gs:// notation.
--app-package=APP_PACKAGE
(REMOVED) The Java package of the application under test. By default,
the application package name is parsed from the APK manifest.
Flag --app-package has been removed.
--async
Invoke a test asynchronously without waiting for test results.
--auto-google-login
Automatically log into the test device using a preconfigured Google
account before beginning the test. Enabled by default, use
--no-auto-google-login to disable.
--directories-to-pull=[DIR_TO_PULL,...]
A list of paths that will be copied from the device's storage to the
designated results bucket after the test is complete. These must be
absolute paths under /sdcard, /storage, or /data/local/tmp (for
example, --directories-to-pull
/sdcard/tempDir1,/data/local/tmp/tempDir2). Path names are restricted
to the characters a-zA-Z0-9_-./+. The paths /sdcard and /data will be
made available and treated as implicit path substitutions. E.g. if
/sdcard on a particular device does not map to external storage, the
system will replace it with the external storage path prefix for that
device. Note that access to some directories on API levels 29 and later
may also be limited by scoped storage rules.
--environment-variables=[KEY=VALUE,...]
A comma-separated, key=value map of environment variables and their
desired values. The environment variables are mirrored as extra options
to the am instrument -e KEY1 VALUE1 ... command and passed to your test
runner (typically AndroidJUnitRunner). Examples:
Enable code coverage and provide a directory to store the coverage
results when using Android Test Orchestrator (--use-orchestrator):
--environment-variables clearPackageData=true,coverage=true,coverageFilePath=/sdcard/
Enable code coverage and provide a file path to store the coverage
results when not using Android Test Orchestrator
(--no-use-orchestrator):
--environment-variables coverage=true,coverageFile=/sdcard/coverage.ec
Note: If you need to embed a comma into a VALUE string, please refer to
gcloud topic escaping for ways to change the default list delimiter.
--network-profile=PROFILE_ID
The name of the network traffic profile, for example
--network-profile=LTE, which consists of a set of parameters to emulate
network conditions when running the test (default: no network shaping;
see available profiles listed by the $ gcloud firebase test
network-profiles list command). This feature only works on physical
devices.
--num-flaky-test-attempts=int
Specifies the number of times a test execution should be reattempted if
one or more of its test cases fail for any reason. An execution that
initially fails but succeeds on any reattempt is reported as FLAKY.
The maximum number of reruns allowed is 10. (Default: 0, which implies
no reruns.) All additional attempts are executed in parallel.
--obb-files=OBB_FILE,[OBB_FILE]
A list of one or two Android OBB file names which will be copied to
each test device before the tests will run (default: None). Each OBB
file name must conform to the format as specified by Android (e.g.
[main|patch].0300110.com.example.android.obb) and will be installed
into <shared-storage>/Android/obb/<package-name>/ on the test device.
--other-files=DEVICE_PATH=FILE_PATH,[...]
A list of device-path=file-path pairs that indicate the device paths to
push files to the device before starting tests, and the paths of files
to push.
Device paths must be under absolute, approved paths
(${EXTERNAL_STORAGE}, or ${ANDROID_DATA}/local/tmp). Source file paths
may be in the local filesystem or in Google Cloud Storage (gs://...).
Examples:
--other-files /sdcard/dir1/file1.txt=local/file.txt,/storage/dir2/file2.jpg=gs://bucket/file.jpg
This flag only copies files to the device. To install files, like OBB
or APK files, see --obb-files and --additional-apks.
--performance-metrics
Monitor and record performance metrics: CPU, memory, network usage, and
FPS (game-loop only). Enabled by default, use --no-performance-metrics
to disable.
--record-video
Enable video recording during the test. Enabled by default, use
--no-record-video to disable.
--results-bucket=RESULTS_BUCKET
The name of a Google Cloud Storage bucket where raw test results will
be stored (default: "test-lab-<random-UUID>"). Note that the bucket
must be owned by a billing-enabled project, and that using a
non-default bucket will result in billing charges for the storage used.
--results-dir=RESULTS_DIR
The name of a unique Google Cloud Storage object within the results
bucket where raw test results will be stored (default: a timestamp with
a random suffix). Caution: if specified, this argument must be unique
for each test matrix you create, otherwise results from multiple test
matrices will be overwritten or intermingled.
--results-history-name=RESULTS_HISTORY_NAME
The history name for your test results (an arbitrary string label;
default: the application's label from the APK manifest). All tests
which use the same history name will have their results grouped
together in the Firebase console in a time-ordered test history list.
ANDROID GAME-LOOP TEST FLAGS
--scenario-labels=LABEL,[LABEL,...]
A list of game-loop scenario labels (default: None). Each game-loop
scenario may be labeled in the APK manifest file with one or more
arbitrary strings, creating logical groupings (e.g.
GPU_COMPATIBILITY_TESTS). If --scenario-numbers and --scenario-labels
are specified together, Firebase Test Lab will first execute each
scenario from --scenario-numbers. It will then expand each given
scenario label into a list of scenario numbers marked with that label,
and execute those scenarios.
--scenario-numbers=int,[int,...]
A list of game-loop scenario numbers which will be run as part of the
test (default: all scenarios). A maximum of 1024 scenarios may be
specified in one test matrix, but the maximum number may also be
limited by the overall test --timeout setting.
ANDROID INSTRUMENTATION TEST FLAGS
--test-package=TEST_PACKAGE
(REMOVED) The Java package name of the instrumentation test. By
default, the test package name is parsed from the APK manifest.
Flag --test-package has been removed.
--test-runner-class=TEST_RUNNER_CLASS
The fully-qualified Java class name of the instrumentation test runner
(default: the last name extracted from the APK manifest).
--test-targets=TEST_TARGET,[TEST_TARGET,...]
A list of one or more test target filters to apply (default: run all
test targets). Each target filter must be fully qualified with the
package name, class name, or test annotation desired. Any test filter
supported by am instrument -e ... is supported. See
https://developer.android.com/reference/android/support/test/runner/AndroidJUnitRunner
for more information. Examples:
◆ --test-targets "package com.my.package.name"
◆ --test-targets "notPackage com.package.to.skip"
◆ --test-targets "class com.foo.ClassName"
◆ --test-targets "notClass com.foo.ClassName#testMethodToSkip"
◆ --test-targets "annotation com.foo.AnnotationToRun"
◆ --test-targets "size large notAnnotation com.foo.AnnotationToSkip"
--use-orchestrator
Whether each test runs in its own Instrumentation instance with the
Android Test Orchestrator (default: Orchestrator is not used, same as
specifying --no-use-orchestrator). Orchestrator is only compatible with
AndroidJUnitRunner v1.1 or higher. See
https://developer.android.com/training/testing/junit-runner.html#using-android-test-orchestrator
for more information about Android Test Orchestrator.
ANDROID ROBO TEST FLAGS
--robo-directives=[TYPE:RESOURCE_NAME=INPUT,...]
A comma-separated (<type>:<key>=<value>) map of robo_directives that
you can use to customize the behavior of Robo test. The type specifies
the action type of the directive, which may take on values click, text
or ignore. If no type is provided, text will be used by default. Each
key should be the Android resource name of a target UI element and each
value should be the text input for that element. Values are only
permitted for text type elements, so no value should be specified for
click and ignore type elements. No more than one click element is
allowed.
To provide custom login credentials for your app, use
--robo-directives text:username_resource=username,text:password_resource=password
To instruct Robo to click on the sign-in button, use
--robo-directives click:sign_in_button=
To instruct Robo to ignore any UI elements with resource names which
equal or start with the user-defined value, use
--robo-directives ignore:ignored_ui_element_resource_name=
To learn more about Robo test and robo_directives, see
https://firebase.google.com/docs/test-lab/android/command-line#custom_login_and_text_input_with_robo_test.
Caution: You should only use credentials for test accounts that are not
associated with real users.
--robo-script=ROBO_SCRIPT
The path to a Robo Script JSON file. The path may be in the local
filesystem or in Google Cloud Storage using gs:// notation. You can
guide the Robo test to perform specific actions by recording a Robo
Script in Android Studio and then specifying this argument. Learn more
at https://firebase.google.com/docs/test-lab/robo-ux-test#scripting.
DEPRECATED DEVICE DIMENSIONS FLAGS
--device-ids=MODEL_ID,[MODEL_ID,...], -d MODEL_ID,[MODEL_ID,...]
The list of MODEL_IDs to test against (default: one device model
determined by the Firebase Test Lab device catalog; see TAGS listed by
the $ gcloud firebase test android devices list command).
--locales=LOCALE,[LOCALE,...], -l LOCALE,[LOCALE,...]
The list of LOCALEs to test against (default: a single locale
determined by the Firebase Test Lab device catalog).
--orientations=ORIENTATION,[ORIENTATION], -o ORIENTATION,[ORIENTATION]
The device orientation(s) to test against (default: portrait).
Specifying 'default' will pick the preferred orientation for the app.
ORIENTATION must be one of: portrait, landscape, default.
--os-version-ids=OS_VERSION_ID,[...], -v OS_VERSION_ID,[...]
The list of OS_VERSION_IDs to test against (default: a version ID
determined by the Firebase Test Lab device catalog).
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test android run
$ gcloud beta firebase test android run

36
gcloud/firebase/test/android/versions/describe Normal file
View file

@ -0,0 +1,36 @@
NAME
gcloud firebase test android versions describe - describe an Android OS
version
SYNOPSIS
gcloud firebase test android versions describe VERSION_ID
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Describe an Android OS version.
EXAMPLES
To see attributes of the Android OS version 'my-version', run:
$ gcloud firebase test android versions describe my-version
POSITIONAL ARGUMENTS
VERSION_ID
The version ID to describe, found using $ gcloud firebase test android
versions list.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test android versions describe
$ gcloud beta firebase test android versions describe

42
gcloud/firebase/test/android/versions/help Normal file
View file

@ -0,0 +1,42 @@
NAME
gcloud firebase test android versions - explore Android versions available
for testing
SYNOPSIS
gcloud firebase test android versions COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Explore Android versions available for testing.
EXAMPLES
To list information about all versions of the Android OS available for
running tests, including details such as OS code name and release date,
run:
$ gcloud firebase test android versions list
To view information about a specific Android OS version, run:
$ gcloud firebase test android versions describe VERSION_ID
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
describe
Describe an Android OS version.
list
List all Android OS versions available for testing.
NOTES
These variants are also available:
$ gcloud alpha firebase test android versions
$ gcloud beta firebase test android versions

58
gcloud/firebase/test/android/versions/list Normal file
View file

@ -0,0 +1,58 @@
NAME
gcloud firebase test android versions list - list all Android OS versions
available for testing
SYNOPSIS
gcloud firebase test android versions list [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List all Android OS versions available for testing.
EXAMPLES
To list all versions available for testing, run:
$ gcloud firebase test android versions list
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test android versions list
$ gcloud beta firebase test android versions list

35
gcloud/firebase/test/help Normal file
View file

@ -0,0 +1,35 @@
NAME
gcloud firebase test - interact with Firebase Test Lab
SYNOPSIS
gcloud firebase test GROUP [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Explore devices and OS versions available as test targets, run tests,
monitor test progress, and view detailed test results in the Firebase
console.
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
GROUPS
GROUP is one of the following:
android
Command group for Android application testing.
ios
Command group for iOS application testing.
network-profiles
Explore network profiles available for testing.
NOTES
These variants are also available:
$ gcloud alpha firebase test
$ gcloud beta firebase test

62
gcloud/firebase/test/ios/help Normal file
View file

@ -0,0 +1,62 @@
NAME
gcloud firebase test ios - command group for iOS application testing
SYNOPSIS
gcloud firebase test ios GROUP | COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Explore physical iOS devices and iOS versions which are available as test
targets. Also run tests against your iOS app on these devices, monitor your
test progress, and view detailed test results in the Firebase console.
EXAMPLES
To see a list of available iOS devices and supported iOS versions, run:
$ gcloud firebase test ios models list
To view information about a specific iOS model, run:
$ gcloud firebase test ios models describe MODEL_ID
To view details about all iOS versions, run:
$ gcloud firebase test ios versions list
To view information about a specific iOS version, run:
$ gcloud firebase test ios versions describe VERSION_ID
To view all options available for iOS tests, run:
$ gcloud firebase test ios run --help
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
GROUPS
GROUP is one of the following:
locales
Explore iOS locales available for testing.
models
Explore iOS models available in the Test Environment catalog.
versions
Explore iOS versions available for testing.
COMMANDS
COMMAND is one of the following:
run
Invoke a test in Firebase Test Lab for iOS and view test results.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios
$ gcloud beta firebase test ios

38
gcloud/firebase/test/ios/locales/describe Normal file
View file

@ -0,0 +1,38 @@
NAME
gcloud firebase test ios locales describe - describe an iOS locale
SYNOPSIS
gcloud firebase test ios locales describe LOCALE [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Describe an iOS locale.
EXAMPLES
To describe an iOS locale, run:
gcloud firebase test ios locales describe es_419
To describe an iOS locale in JSON format, run:
gcloud firebase test ios locales describe es_419 --format=json
POSITIONAL ARGUMENTS
LOCALE
The locale to describe, found using $ gcloud firebase test ios locales
list.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios locales describe
$ gcloud beta firebase test ios locales describe

41
gcloud/firebase/test/ios/locales/help Normal file
View file

@ -0,0 +1,41 @@
NAME
gcloud firebase test ios locales - explore iOS locales available for
testing
SYNOPSIS
gcloud firebase test ios locales COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Explore iOS locales available for testing.
EXAMPLES
To list all available iOS locales which can be used for testing
international applications, run:
$ gcloud firebase test ios locales list
To view information about a specific locale, run:
$ gcloud firebase test ios locales describe LOCALE
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
describe
Describe an iOS locale.
list
List all iOS locales available for testing internationalized apps.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios locales
$ gcloud beta firebase test ios locales

62
gcloud/firebase/test/ios/locales/list Normal file
View file

@ -0,0 +1,62 @@
NAME
gcloud firebase test ios locales list - list all iOS locales available for
testing internationalized apps
SYNOPSIS
gcloud firebase test ios locales list [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List all iOS locales available for testing internationalized apps.
EXAMPLES
To list all available locales which can be used for testing
internationalized iOS applications, run:
$ gcloud firebase test ios locales list
To filter the locales to see only Spanish-speaking regions, run:
$ gcloud firebase test ios locales list --filter=Spanish
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios locales list
$ gcloud beta firebase test ios locales list

38
gcloud/firebase/test/ios/models/describe Normal file
View file

@ -0,0 +1,38 @@
NAME
gcloud firebase test ios models describe - describe an iOS model
SYNOPSIS
gcloud firebase test ios models describe MODEL_ID [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Describe an iOS model.
EXAMPLES
To describe an iOS model, run:
gcloud firebase test ios models describe iphone7
To describe an iOS model in JSON format, run:
gcloud firebase test ios models describe iphone7 --format=json
POSITIONAL ARGUMENTS
MODEL_ID
ID of the model to describe, found using $ gcloud firebase test ios
models list.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios models describe
$ gcloud beta firebase test ios models describe

41
gcloud/firebase/test/ios/models/help Normal file
View file

@ -0,0 +1,41 @@
NAME
gcloud firebase test ios models - explore iOS models available in the Test
Environment catalog
SYNOPSIS
gcloud firebase test ios models COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Explore iOS models available in the Test Environment catalog.
EXAMPLES
To list all iOS models available for running tests, along with their model
names and supported iOS versions, run:
$ gcloud firebase test ios models list
To view information about a single iOS model, run:
$ gcloud firebase test ios models describe MODEL_ID
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
describe
Describe an iOS model.
list
List all iOS models available for testing.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios models
$ gcloud beta firebase test ios models

57
gcloud/firebase/test/ios/models/list Normal file
View file

@ -0,0 +1,57 @@
NAME
gcloud firebase test ios models list - list all iOS models available for
testing
SYNOPSIS
gcloud firebase test ios models list [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List all iOS models available for testing.
EXAMPLES
To list all iOS models available for testing, run:
gcloud firebase test ios models list
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios models list
$ gcloud beta firebase test ios models list

213
gcloud/firebase/test/ios/run Normal file
View file

@ -0,0 +1,213 @@
NAME
gcloud firebase test ios run - invoke a test in Firebase Test Lab for iOS
and view test results
SYNOPSIS
gcloud firebase test ios run [ARGSPEC] [--device=DIMENSION=VALUE,[...]]
[--test=XCTEST_ZIP] [--timeout=TIMEOUT] [--type=TYPE]
[--xcode-version=XCODE_VERSION] [--xctestrun-file=XCTESTRUN_FILE]
[--async] [--num-flaky-test-attempts=int] [--record-video]
[--results-bucket=RESULTS_BUCKET] [--results-dir=RESULTS_DIR]
[--results-history-name=RESULTS_HISTORY_NAME]
[--test-special-entitlements] [--filter=EXPRESSION] [--limit=LIMIT]
[--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]] [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
gcloud firebase test ios run invokes and monitors tests in Firebase Test
Lab for iOS.
The currently supported iOS test frameworks are XCTest and XCUITest. Other
iOS testing frameworks which are built upon XCTest and XCUITest should also
work.
The XCTEST_ZIP test package is a zip file built using Apple's Xcode and
supporting tools. For a detailed description of the process to create your
XCTEST_ZIP file, see
https://firebase.google.com/docs/test-lab/ios/command-line.
All arguments for gcloud firebase test ios run may be specified on the
command line and/or within an argument file. Run $ gcloud topic arg-files
for more information about argument files.
EXAMPLES
To invoke an XCTest lasting up to five minutes against the default device
environment, run:
$ gcloud firebase test ios run --test=XCTEST_ZIP --timeout=5m
To invoke an XCTest against an iPad 5 running iOS 11.2, run:
$ gcloud firebase test ios run --test=XCTEST_ZIP \
--device=model=ipad5,version=11.2
To run your tests against multiple iOS devices simultaneously, specify the
--device flag more than once:
$ gcloud firebase test ios run --test=XCTEST_ZIP \
--device=model=iphone7 --device=model=ipadmini4,version=11.2 \
--device=model=iphonese
To run your XCTest using a specific version of Xcode, say 9.4.1, run:
$ gcloud firebase test ios run --test=XCTEST_ZIP \
--xcode-version=9.4.1
All test arguments for a given test may alternatively be stored in an
argument group within a YAML-formatted argument file. The ARG_FILE may
contain one or more named argument groups, and argument groups may be
combined using the include: attribute (Run $ gcloud topic arg-files for
more information). The ARG_FILE can easily be shared with colleagues or
placed under source control to ensure consistent test executions.
To run a test using arguments loaded from an ARG_FILE named
excelsior_app_args, which contains an argument group named ios-args:, use
the following syntax:
$ gcloud firebase test ios run path/to/excelsior_app_args:ios-args
POSITIONAL ARGUMENTS
[ARGSPEC]
An ARG_FILE:ARG_GROUP_NAME pair, where ARG_FILE is the path to a file
containing groups of test arguments in yaml format, and ARG_GROUP_NAME
is the particular yaml object holding a group of arg:value pairs to
use. Run $ gcloud topic arg-files for more information and examples.
COMMONLY USED FLAGS
--device=DIMENSION=VALUE,[...]
A list of DIMENSION=VALUE pairs which specify a target device to test
against. This flag may be repeated to specify multiple devices. The
device dimensions are: model, version, locale, and orientation. If any
dimensions are omitted, they will use a default value. The default
value, and all possible values, for each dimension can be found with
the list command for that dimension, such as $ gcloud firebase test ios
models list. Omitting this flag entirely will run tests against a
single device using defaults for every dimension.
Examples:
--device model=iphone8plus
--device version=11.2
--device model=ipadmini4,version=11.2,locale=zh_CN,orientation=landscape
--test=XCTEST_ZIP
The path to the test package (a zip file containing the iOS app and
XCTest files). The given path may be in the local filesystem or in
Google Cloud Storage using a URL beginning with gs://. Note: any
.xctestrun file in this zip file will be ignored if --xctestrun-file is
specified.
--timeout=TIMEOUT
The max time this test execution can run before it is cancelled
(default: 15m). It does not include any time necessary to prepare and
clean up the target device. The maximum possible testing time is 45m on
physical devices and 60m on virtual devices. The TIMEOUT units can be
h, m, or s. If no unit is given, seconds are assumed. Examples:
◆ --timeout 1h is 1 hour
◆ --timeout 5m is 5 minutes
◆ --timeout 200s is 200 seconds
◆ --timeout 100 is 100 seconds
--type=TYPE
The type of iOS test to run. TYPE must be one of: xctest, game-loop.
--xcode-version=XCODE_VERSION
The version of Xcode that should be used to run an XCTest. Defaults to
the latest Xcode version supported in Firebase Test Lab. This Xcode
version must be supported by all iOS versions selected in the test
matrix. The list of Xcode versions supported by each version of iOS can
be viewed by running $ gcloud firebase test ios versions list.
--xctestrun-file=XCTESTRUN_FILE
The path to an .xctestrun file that will override any .xctestrun file
contained in the --test package. Because the .xctestrun file contains
environment variables along with test methods to run and/or ignore,
this can be useful for customizing or sharding test suites. The given
path may be in the local filesystem or in Google Cloud Storage using a
URL beginning with gs://.
FLAGS
--async
Invoke a test asynchronously without waiting for test results.
--num-flaky-test-attempts=int
Specifies the number of times a test execution should be reattempted if
one or more of its test cases fail for any reason. An execution that
initially fails but succeeds on any reattempt is reported as FLAKY.
The maximum number of reruns allowed is 10. (Default: 0, which implies
no reruns.) All additional attempts are executed in parallel.
--record-video
Enable video recording during the test. Enabled by default, use
--no-record-video to disable.
--results-bucket=RESULTS_BUCKET
The name of a Google Cloud Storage bucket where raw test results will
be stored (default: "test-lab-<random-UUID>"). Note that the bucket
must be owned by a billing-enabled project, and that using a
non-default bucket will result in billing charges for the storage used.
--results-dir=RESULTS_DIR
The name of a unique Google Cloud Storage object within the results
bucket where raw test results will be stored (default: a timestamp with
a random suffix). Caution: if specified, this argument must be unique
for each test matrix you create, otherwise results from multiple test
matrices will be overwritten or intermingled.
--results-history-name=RESULTS_HISTORY_NAME
The history name for your test results (an arbitrary string label;
default: the bundle ID for the iOS application). All tests which use
the same history name will have their results grouped together in the
Firebase console in a time-ordered test history list.
--test-special-entitlements
Enables testing special app entitlements. Re-signs an app having
special entitlements with a new application-identifier. This currently
supports testing Push Notifications (aps-environment) entitlement for
up to one app in a project.
Note: Because this changes the app's identifier, make sure none of the
resources in your zip file contain direct references to the test app's
bundle id.
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios run
$ gcloud beta firebase test ios run

41
gcloud/firebase/test/ios/versions/describe Normal file
View file

@ -0,0 +1,41 @@
NAME
gcloud firebase test ios versions describe - describe an iOS operating
system version
SYNOPSIS
gcloud firebase test ios versions describe VERSION_ID
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Describe an iOS operating system version.
EXAMPLES
To describe an iOS operating system version available for testing, run:
gcloud firebase test ios versions describe 12.1
To describe an iOS operating system version available for testing in JSON
format, run:
gcloud firebase test ios versions describe 12.1 --format=json
POSITIONAL ARGUMENTS
VERSION_ID
The version ID to describe, found using $ gcloud firebase test ios
versions list.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios versions describe
$ gcloud beta firebase test ios versions describe

41
gcloud/firebase/test/ios/versions/help Normal file
View file

@ -0,0 +1,41 @@
NAME
gcloud firebase test ios versions - explore iOS versions available for
testing
SYNOPSIS
gcloud firebase test ios versions COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Explore iOS versions available for testing.
EXAMPLES
To list information about all versions of iOS available for running tests,
including details such as OS major and minor versions, run:
$ gcloud firebase test ios versions list
To view information about a specific version of iOS, run:
$ gcloud firebase test ios versions describe VERSION_ID
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
describe
Describe an iOS operating system version.
list
List all iOS versions available for testing.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios versions
$ gcloud beta firebase test ios versions

62
gcloud/firebase/test/ios/versions/list Normal file
View file

@ -0,0 +1,62 @@
NAME
gcloud firebase test ios versions list - list all iOS versions available
for testing
SYNOPSIS
gcloud firebase test ios versions list [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List all iOS versions available for testing.
EXAMPLES
To list all iOS versions available for testing, run:
gcloud firebase test ios versions list
To filter major versions available for testing, run:
gcloud firebase test ios versions list --filter=majorVersion:12
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios versions list
$ gcloud beta firebase test ios versions list

42
gcloud/firebase/test/network-profiles/describe Normal file
View file

@ -0,0 +1,42 @@
NAME
gcloud firebase test network-profiles describe - describe a network profile
SYNOPSIS
gcloud firebase test network-profiles describe PROFILE_ID
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
Describe a network profile.
Run $ gcloud firebase test network-profiles --help for descriptions of the
network profile parameters.
EXAMPLES
To describe a network profile, run:
gcloud firebase test network-profiles describe GSM
To describe a network profiles in JSON format, run:
gcloud firebase test network-profiles describe GSM --format=json
POSITIONAL ARGUMENTS
PROFILE_ID
The network profile to describe, found using $ gcloud firebase test
network-profiles list.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test network-profiles describe
$ gcloud beta firebase test network-profiles describe

54
gcloud/firebase/test/network-profiles/help Normal file
View file

@ -0,0 +1,54 @@
NAME
gcloud firebase test network-profiles - explore network profiles available
for testing
SYNOPSIS
gcloud firebase test network-profiles COMMAND [GCLOUD_WIDE_FLAG ...]
DESCRIPTION
A network traffic profile consists of a set of parameters to emulate
network conditions when running a test. This feature only works on physical
devices. The network shaping parameters are:
▪ RULE: Where to apply traffic shaping. The UP rule shapes the
connection from the device to the internet. The DOWN rule shapes the
connection from the internet to the device.
▪ DELAY: The delay in packet transmission, in ms.
▪ LOSS_RATIO: The ratio of packets dropped during transmission.
▪ DUPLICATION_RATIO: The ratio of packets duplicated during
transmission.
▪ BANDWIDTH: The average packet transmission rate in kbits/s, as
defined by the token bucket algorithm.
▪ BURST: The total size, in kbits, by which packets can exceed the
bandwidth, as defined by the token bucket algorithm.
EXAMPLES
To list all network profiles which can be used for testing, run:
$ gcloud firebase test network-profiles list
To view information about a specific network profile, run:
$ gcloud firebase test network-profiles describe PROFILE_ID
GCLOUD WIDE FLAGS
These flags are available to all commands: --help.
Run $ gcloud help for details.
COMMANDS
COMMAND is one of the following:
describe
Describe a network profile.
list
List all network profiles available for testing.
NOTES
These variants are also available:
$ gcloud alpha firebase test network-profiles
$ gcloud beta firebase test network-profiles

65
gcloud/firebase/test/network-profiles/list Normal file
View file

@ -0,0 +1,65 @@
NAME
gcloud firebase test network-profiles list - list all network profiles
available for testing
SYNOPSIS
gcloud firebase test network-profiles list [--filter=EXPRESSION]
[--limit=LIMIT] [--page-size=PAGE_SIZE] [--sort-by=[FIELD,...]]
[GCLOUD_WIDE_FLAG ...]
DESCRIPTION
List all network profiles available for testing.
Run $ gcloud firebase test network-profiles --help for descriptions of the
network profile parameters.
EXAMPLES
To list all network profiles, run:
gcloud firebase test network-profiles list
To list all GSM network profiles, run:
gcloud firebase test network-profiles list --filter="id:GSM"
LIST COMMAND FLAGS
--filter=EXPRESSION
Apply a Boolean filter EXPRESSION to each resource item to be listed.
If the expression evaluates True, then that item is listed. For more
details and examples of filter expressions, run $ gcloud topic filters.
This flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--limit=LIMIT
Maximum number of resources to list. The default is unlimited. This
flag interacts with other flags that are applied in this order:
--flatten, --sort-by, --filter, --limit.
--page-size=PAGE_SIZE
Some services group resource list output into pages. This flag
specifies the maximum number of resources per page. The default is
determined by the service if it supports paging, otherwise it is
unlimited (no paging). Paging may be applied before or after --filter
and --limit depending on the service.
--sort-by=[FIELD,...]
Comma-separated list of resource field key names to sort by. The
default order is ascending. Prefix a field with ``~'' for descending
order on that field. This flag interacts with other flags that are
applied in this order: --flatten, --sort-by, --filter, --limit.
GCLOUD WIDE FLAGS
These flags are available to all commands: --access-token-file, --account,
--billing-project, --configuration, --flags-file, --flatten, --format,
--help, --impersonate-service-account, --log-http, --project, --quiet,
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test network-profiles list
$ gcloud beta firebase test network-profiles list