5SrSSKJr SSKJr SSKJr SSKJr SSKJr SSKJr SSKJ r SS KJ r SS KJ r SS KJ r SS KJ r SS KJr SSKJr SSKJr SSKJr SSKJr SSKrSr\R0\R2"\R4R65"SS\R8555rSr\R2"\R4R>\R4R@5"SS\55r!g)z+The 'gcloud firebase test ios run' command.)absolute_import)division)unicode_literals)arg_util)ctrl_c_handler exit_code)history_picker) matrix_ops)results_bucket)results_summary) tool_results)util) arg_manager)matrix_creator)base)logNzapplication/octet-streamc8\rSrSrSrSSS.r\S5rSrSr g ) Run'AInvoke a test in Firebase Test Lab for iOS and view test results.a *{command}* 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 *{command}* may be specified on the command line and/or within an argument file. Run *$ gcloud topic arg-files* for more information about argument files. a To invoke an XCTest lasting up to five minutes against the default device environment, run: $ {command} --test=XCTEST_ZIP --timeout=5m To invoke an XCTest against an iPad 5 running iOS 11.2, run: $ {command} --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: $ {command} --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: $ {command} --test=XCTEST_ZIP --xcode-version=9.4.1 To help you identify and locate your test matrix in the Firebase console, run: $ {command} --test=XCTEST_ZIP --client-details=matrixLabel="Example matrix label" 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: $ {command} path/to/excelsior_app_args:ios-args  DESCRIPTIONEXAMPLESc[R"U5 [R"U5 [RR U5 UR R[R5 g)zMethod called by Calliope to register flags for this command. Args: parser: An argparse parser used to add arguments that follow this command in the CLI. Positional arguments are allowed. N) rAddCommonTestRunArgsAddIosTestArgsrURI_FLAGRemoveFromParser display_info AddFormatrOUTCOMES_FORMAT)parsers $lib/surface/firebase/test/ios/run.pyArgsRun.ArgsesL !!&) F#MM""6* !!$"6"67c  UR(aURS5(dSUl[RR S5 [ R"5RU5 [R"5nURSnURSnURSn[R"X!RURUXE5nUR(a UR!UR["5 UR$(aUR!UR$S5 UR&(aUR!UR&S5 [)US S 5=(d /nUHnUR!U["5 M [)US 05=(d 0n [*R,"U 5HHupU n S U ;aXR/S 5S -S n UR!U S [R0"U 5S9 MJ [)USS 5(aUR!UR2S5 UR55 [6R8"X#U5n [;U5nU R=U5n[>R@"XRUURB[*RD"URG555n[HRJ"URLURNUR5n[PRR"U5 URUU5n[VRX"UU5n[VRZ"UU5n[RR S5 UR(a UsS S S 5 $[RR SRU55 []U5S :Xa/UR^S:XaURaUSRb5 OURe5 S S S 5 [RR SRW55 [fRh"X#UWURL5n[jRl"URo5URpRr5Ul5URu5$!,(df  N=f)a}Run the 'firebase test ios run' command to invoke a test in Test Lab. Args: args: an argparse namespace. All the arguments that were provided to this command invocation (i.e. group and command arguments combined). Returns: One of: - a list of TestOutcome tuples (if ToolResults are available). - a URL string pointing to the user's results in ToolResults or GCS. formatzW value(format('Final test results will be available at [ {0} ].', [])) z] Have questions, feedback, or issues? Get support by emailing: ftl-ios-feedback@google.com toolresults_clienttoolresults_messagesstorage_clientzapplication/zipztext/xmladditional_ipasN other_files:)destination_object robo_scriptzapplication/jsonz)Test results will be streamed to [ {0} ].rz' More details are available at [ {0} ].);async_ IsSpecifiedr)rstatusPrintrIosArgsManagerPreparer GetProjectcontextr ResultsBucketOps results_dirappUploadFileToGcs_IPA_MIME_TYPEtestxctestrun_filegetattrsix iteritemsfindGetRelativeDevicePathr2LogGcsResultsUrlr ToolResultsHistoryPickerPickHistoryNameGetToolResultsHistoryIdr CreateMatrixgcs_results_root text_type ReleaseTrackr MatrixMonitor testMatrixIdtyperCancellableTestSectionHandleUnsupportedExecutionsrGetToolResultsIdsCreateToolResultsUiUrllennum_flaky_test_attemptsMonitorTestExecutionProgressidMonitorTestMatrixProgressr ToolResultsSummaryFetcherr ExitCodeFromRollupOutcomeFetchMatrixRollupOutcomeOutcomeSummaryValueValuesEnum+CreateMatrixOutcomeSummaryUsingEnvironments)selfargsproject tr_client tr_messagesr, bucket_opsr-additional_ipar. device_pathfile_to_uploadpathtr_history_picker history_name history_idmatrixmonitorsupported_executionstr_idsurlsummary_fetchers r$rRun.Runrs {{4++H55 dkJJBC ((.ooG 12I,,56K\\"23N00:M:M151A1A91<NJ xx  >: yy  ,=>   !4!4jAd$5t<BO)  @*$ r28bK'*}}['A# d IIcNQ&'(   !77=!? (Bt]D))  !1!13EF!&??K)"4(L"::<HJ  ( (||Z)3)D)D),t7H7H7J)KMF&&v':':DII'+||5G  . .w 7$@@H--fg>f  / / @c jjr  8 7 jjBII#NO ! "a 'D,H,HA,M,,-A!-D-G-GH))+ 8 JJ?FFsKL&??K1D1DFO88002224DN  F F HH1 8 7s%A1S AUR(a UR$g)aCReturns the results history name to use to look up a history ID. The history ID corresponds to a history name. If the user provides their own history name, we use that to look up the history ID; Otherwise, we punt and let the Testing service determine the appropriate history ID to publish to. Args: args: an argparse namespace. All the arguments that were provided to the command invocation (i.e. group and command arguments combined). Returns: Either a string containing a history name derived from user-supplied data, or None if we lack the required information. N)results_history_name)rcs r$rJrJs   $ $$ r'c@^\rSrSrSrSSS.r\U4Sj5rSrU=r $)RunBetara *{command}* invokes and monitors tests in Firebase Test Lab for iOS. Two types of iOS tests are currently supported: - *xctest*: corresponds to the XCTest and XCUITest frameworks. 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. - *game-loop*: launches the game app through a custom URL scheme to execute a "demo mode" built into the game app that simulates actions of a real player. This test type can include multiple game loops (also called "scenarios") indicated by positive numbers. The type of test to run can be specified with the *--type* flag, which defaults to `xctest`. All arguments for *{command}* may be specified on the command line and/or within an argument file. Run *$ gcloud topic arg-files* for more information about argument files. a To help you identify and locate your test matrix in the Firebase console, run: $ {command} --test=XCTEST_ZIP --client-details=matrixLabel="Example matrix label" To invoke an XCTest lasting up to five minutes against the default device environment, run: $ {command} --test=XCTEST_ZIP --timeout=5m To invoke an XCTest against an iPad 5 running iOS 11.2, run: $ {command} --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: $ {command} --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: $ {command} --test=XCTEST_ZIP --xcode-version=9.4.1 To help you identify and locate your test matrix in the Firebase console, run: $ {command} --test=XCTEST_ZIP --client-details=matrixLabel="Example matrix label" To run an iOS game loop, specify the *--type* and *--app* flags: $ {command} --type=game-loop --app=app.ipa To run an iOS game loop with specific scenario(s), use the *--scenario-numbers* flag: $ {command} --type=game-loop --app=app.ipa --scenario-numbers=1,2,3 To run a test that pushes a local file onto the device before testing, use the *--other-files* flag: $ {command} --type=game-loop --app=app.ipa --scenario-numbers=1 --other-files=/private/var/mobile/Media/file.txt=/path/to/file.txt 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: $ {command} path/to/excelsior_app_args:ios-args rc>[[[] U5 [R"U5 [R "U5 g)N)superrr%rAddIosBetaArgs AddBetaArgs)r# __class__s r$r% RunBeta.Args7s. '7 ( F#  r'r~) rvrwrxryrzr{r|r%r} __classcell__)rs@r$rrs-I .91R-h!!r'r)"rz __future__rrr$googlecloudsdk.api_lib.firebase.testrrr r r r r rr(googlecloudsdk.api_lib.firebase.test.iosrrgooglecloudsdk.calliopergooglecloudsdk.corerrDr@UnicodeIsSupported ReleaseTracksrOGA ListCommandrrJALPHABETArr~r'r$rs2&'9?:?;?@=5@C(# +D%%(()`I$  `I*`IF(D%%++T->->-C-CDZ!cZ!EZ!r'