Update documentation

google_testing1_cli/projects_test-matrices-create/index.html

@@ -5,7 +5,7 @@
   <meta charset="utf-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
   
-  <title>Test Matrices Create - testing v2.0.4+20210326</title>
+  <title>Test Matrices Create - testing v3.0.0+20220301</title>
   
 
   
@@ -34,7 +34,7 @@
     
     <nav data-toggle="wy-nav-shift" class="wy-nav-side stickynav">
       <div class="wy-side-nav-search">
-        <a href=".." class="icon icon-home"> testing v2.0.4+20210326</a>
+        <a href=".." class="icon icon-home"> testing v3.0.0+20220301</a>
         
       </div>
 
@@ -209,8 +209,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
           gcs-path: string
       app-initial-activity: string
       app-package-id: string
-      max-depth: integer
-      max-steps: integer
+      robo-mode: string
       robo-script:
         gcs-path: string
     android-test-loop:
@@ -371,7 +370,7 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 </ul>
 </li>
 <li><code>orchestrator-option=sed</code><ul>
-<li>The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not. <strong> Orchestrator is only compatible with AndroidJUnitRunner version 1.0 or higher! </strong> Orchestrator offers the following benefits: - No shared state - Crashes are isolated - Logs are scoped per test See for more information about Android Test Orchestrator. If not set, the test will be run without the orchestrator.</li>
+<li>The option of whether running each test within its own invocation of instrumentation with Android Test Orchestrator or not. <strong> Orchestrator is only compatible with AndroidJUnitRunner version 1.1 or higher! </strong> Orchestrator offers the following benefits: - No shared state - Crashes are isolated - Logs are scoped per test See for more information about Android Test Orchestrator. If not set, the test will be run without the orchestrator.</li>
 </ul>
 </li>
 <li>
@@ -425,45 +424,41 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 <li>The java package for the application under test. The default value is determined by examining the application&#39;s manifest.</li>
 </ul>
 </li>
-<li><code>max-depth=2</code><ul>
-<li>The max depth of the traversal stack Robo can explore. Needs to be at least 2 to make Robo explore the app beyond the first activity. Default is 50.</li>
-</ul>
-</li>
-<li><code>max-steps=45</code><ul>
-<li>The max number of steps Robo can execute. Default is no limit.</li>
+<li><code>robo-mode=dolor</code><ul>
+<li>The mode in which Robo should run. Most clients should allow the server to populate this field automatically.</li>
 </ul>
 </li>
 <li>
-<p><code>robo-script    gcs-path=eos</code></p>
+<p><code>robo-script    gcs-path=lorem</code></p>
 <ul>
 <li>A path to a file in Google Cloud Storage. Example: gs://build-app-1414623860166/app%40debug-unaligned.apk These paths are expected to be url encoded (percent encoding)</li>
 </ul>
 </li>
 <li>
-<p><code>...android-test-loop.app-apk    gcs-path=labore</code></p>
+<p><code>...android-test-loop.app-apk    gcs-path=eos</code></p>
 <ul>
 <li>A path to a file in Google Cloud Storage. Example: gs://build-app-1414623860166/app%40debug-unaligned.apk These paths are expected to be url encoded (percent encoding)</li>
 </ul>
 </li>
 <li>
-<p><code>..app-bundle.bundle-location    gcs-path=sed</code></p>
+<p><code>..app-bundle.bundle-location    gcs-path=labore</code></p>
 <ul>
 <li>A path to a file in Google Cloud Storage. Example: gs://build-app-1414623860166/app%40debug-unaligned.apk These paths are expected to be url encoded (percent encoding)</li>
 </ul>
 </li>
 <li>
-<p><code>...    app-package-id=duo</code></p>
+<p><code>...    app-package-id=sed</code></p>
 <ul>
 <li>The java package for the application under test. The default is determined by examining the application&#39;s manifest.</li>
 </ul>
 </li>
-<li><code>scenario-labels=sed</code><ul>
+<li><code>scenario-labels=duo</code><ul>
 <li>The list of scenario labels that should be run during the test. The scenario labels should map to labels defined in the application&#39;s manifest. For example, player_experience and com.google.test.loops.player_experience add all of the loops labeled in the manifest with the com.google.test.loops.player_experience name to the execution. Scenarios can also be specified in the scenarios field.</li>
 <li>Each invocation of this argument appends the given value to the array.</li>
 </ul>
 </li>
 <li>
-<p><code>scenarios=40</code></p>
+<p><code>scenarios=21</code></p>
 <ul>
 <li>The list of scenarios that should be run during the test. The default is all test loops, derived from the application&#39;s manifest.</li>
 <li>Each invocation of this argument appends the given value to the array.</li>
@@ -479,31 +474,31 @@ In the latter case it is advised to set the field-cursor to the data-structure's
 <li>Disables video recording. May reduce test latency.</li>
 </ul>
 </li>
-<li><code>ios-test-loop    app-bundle-id=vero</code><ul>
+<li><code>ios-test-loop    app-bundle-id=et</code><ul>
 <li>Output only. The bundle id for the application under test.</li>
 </ul>
 </li>
 <li>
-<p><code>app-ipa    gcs-path=erat</code></p>
+<p><code>app-ipa    gcs-path=et</code></p>
 <ul>
 <li>A path to a file in Google Cloud Storage. Example: gs://build-app-1414623860166/app%40debug-unaligned.apk These paths are expected to be url encoded (percent encoding)</li>
 </ul>
 </li>
 <li>
-<p><code>..    scenarios=8</code></p>
+<p><code>..    scenarios=25</code></p>
 <ul>
 <li>The list of scenarios that should be run during the test. Defaults to the single scenario 0 if unspecified.</li>
 <li>Each invocation of this argument appends the given value to the array.</li>
 </ul>
 </li>
 <li>
-<p><code>..ios-test-setup    network-profile=duo</code></p>
+<p><code>..ios-test-setup    network-profile=erat</code></p>
 <ul>
 <li>The network traffic profile used for running the test. Available network profiles can be queried by using the NETWORK_CONFIGURATION environment type when calling TestEnvironmentDiscoveryService.GetTestEnvironmentCatalog.</li>
 </ul>
 </li>
 <li>
-<p><code>..ios-xc-test    app-bundle-id=dolore</code></p>
+<p><code>..ios-xc-test    app-bundle-id=sed</code></p>
 <ul>
 <li>Output only. The bundle id for the application under test.</li>
 </ul>