GitBook: [#110] No subject

launchableinc · Jan 13, 2023 · 797588c · 797588c
1 parent 9e9abb3
commit 797588c
Show file tree

Hide file tree

Showing 21 changed files with 11 additions and 15 deletions.
diff --git a/.gitbook/assets/sending-data-diagram (1) (1) (1) (1) (1).png b/.gitbook/assets/sending-data-diagram (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/sending-data-diagram (1) (1) (1) (1) (2).png b/.gitbook/assets/sending-data-diagram (1) (1) (1) (1) (2).png
diff --git a/.gitbook/assets/sending-data-diagram (1) (1) (1) (1) (3).png b/.gitbook/assets/sending-data-diagram (1) (1) (1) (1) (3).png
diff --git a/.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (1) (1).png b/.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (1) (1).png
diff --git a/.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (1) (2).png b/.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (1) (2).png
diff --git a/.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (1) (3).png b/.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (1) (3).png
diff --git a/.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (1) (4).png b/.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (1) (4).png
diff --git a/.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (1) (5).png b/.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (1) (5).png
diff --git a/docs/.gitbook/assets/reused-session (1) (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/reused-session (1) (1) (1) (1) (1) (1) (1).png
diff --git a/docs/.gitbook/assets/session-subset-record-tests (1) (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/session-subset-record-tests (1) (1) (1) (1) (1) (1) (1).png
diff --git a/docs/.gitbook/assets/shift-left-new (1) (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/shift-left-new (1) (1) (1) (1) (1) (1) (1).png
diff --git a/docs/.gitbook/assets/shift-right-simple (1) (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/shift-right-simple (1) (1) (1) (1) (1) (1) (1).png
diff --git a/docs/.gitbook/assets/test-pyramid (1) (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/test-pyramid (1) (1) (1) (1) (1) (1) (1).png
diff --git a/docs/.gitbook/assets/testing-bottleneck-infinity (1) (1) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/testing-bottleneck-infinity (1) (1) (1) (1) (1) (1) (1).png
diff --git a/docs/concepts/subset.md b/docs/concepts/subset.md
@@ -8,7 +8,7 @@ The term 'dynamically selected' refers to the fact that the tests returned in su
 
 A subset is the output of a subset _request_ made using the `launchable subset` CLI command. You make a subset request every time you want to run a subset of tests in your CI pipeline:
 
-![High level flow including a subset request](<../../.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (3).png>)
+![High level flow including a subset request](<../../.gitbook/assets/subsetting-diagram (2) (1) (1) (1) (1) (1) (1).png>)
 
 A subset request takes various inputs:
 

diff --git a/docs/features/predictive-test-selection/faq.md b/docs/features/predictive-test-selection/faq.md
@@ -12,15 +12,15 @@ Software development teams are under pressure to deliver code faster while still
 
 There are numerous approaches to help teams deliver code faster: building a CI pipeline, automating tests, continuously delivering code to production. However, none of these help address the problem that running tests (long or short) is the bottleneck in delivering software.
 
-![Testing: A bottleneck that slows teams down](<../../.gitbook/assets/testing-bottleneck-infinity (1) (1) (1) (1) (1) (2).png>)
+![Testing: A bottleneck that slows teams down](<../../.gitbook/assets/testing-bottleneck-infinity (1) (1) (1) (1) (1) (1).png>)
 
 Launchable's solution is to intelligently prioritize tests to cut down testing times without sacrificing quality. Developers get feedback much earlier in the development cycle. Launchable helps teams ship code faster by _testing_ faster.
 
 ### Where does Launchable Predictive Test Selection fit into my development pipeline?
 
 Launchable Predictive Test Selection is test agnostic - send data from the test suites that cause the most pain in your delivery cycle, and Launchable can help reduce the time it takes to run them - delivering feedback earlier.
 
-![Launchable is test agnostic](<../../.gitbook/assets/test-pyramid (1) (1) (1) (1) (1) (1).png>)
+![Launchable is test agnostic](<../../.gitbook/assets/test-pyramid (1) (1) (1) (1) (1) (2).png>)
 
 #### How do I use Launchable Predictive Test Selection to change my testing lifecycle?
 
@@ -95,7 +95,7 @@ You instrument your build script with 4 commands.
 
 We have built integrations to various test runners to make the process of interacting with Launchable easy. Here is an example of how these commands look when using Maven.
 
-![Using Launchable with Maven](<../../.gitbook/assets/launchable-cli-3- (1) (1) (1) (1) (1).png>)
+![Using Launchable with Maven](<../../.gitbook/assets/launchable-cli-3- (1) (1) (1) (1).png>)
 
 The [Getting started](../../sending-data-to-launchable/using-the-launchable-cli/getting-started/) guide will walk you through each step in detail.
 

diff --git a/...-with-the-launchable-cli/zero-input-subsetting/using-groups-to-split-subsets.md b/...-with-the-launchable-cli/zero-input-subsetting/using-groups-to-split-subsets.md
@@ -103,7 +103,7 @@ In this example we'll continue the scenario from above. We have 3 groups, each w
 
 This diagram shows the flow. First we create a subset from all the tests across all groups. Then we split those into groups. Note the special file `subset-groups.txt` which shows us we can skip component B entirely.
 
-<figure><img src="../../../../../.gitbook/assets/zis-with-groups.png" alt=""><figcaption><p>Entire Zero Input Subsetting flow with --split-by-groups added in</p></figcaption></figure>
+<figure><img src="../../../../../.gitbook/assets/zis-with-groups (1).png" alt=""><figcaption><p>Entire Zero Input Subsetting flow with --split-by-groups added in</p></figcaption></figure>
 
 {% hint style="info" %}
 Note that the diagram shows the contents of `subset-component*.txt` as a list of classes. This is the output format for Maven.

diff --git a/docs/policies/security-policies.md b/docs/policies/security-policies.md
@@ -6,7 +6,7 @@ description: Launchable Information Security Policies
 
 Launchable is a multi-tenant SaaS where data is sent from a customer site to Launchable.
 
-![Data flow from customer site to Launchable](<../.gitbook/assets/data-flow (1) (1) (1) (1) (1).png>)
+![Data flow from customer site to Launchable](<../.gitbook/assets/data-flow (1) (1) (1) (1).png>)
 
 This document covers frequently asked questions related to information security (infosec).
 

diff --git a/docs/sending-data-to-launchable/README.md b/docs/sending-data-to-launchable/README.md
@@ -2,10 +2,6 @@
 
 To start using Launchable's features, you need to start sending build and test data from your CI pipeline to your Launchable workspace.
 
-The diagram below diagrams the high-level data flow:
-
-![](<../.gitbook/assets/recording [email protected]>)
-
 ## Integration options
 
 We offer a variety of integration options, depending on your toolchain:

diff --git a/...g-test-results-with-the-launchable-cli/managing-complex-test-session-layouts.md b/...g-test-results-with-the-launchable-cli/managing-complex-test-session-layouts.md
@@ -10,11 +10,11 @@ By default, the Launchable CLI handles creating, saving, and retrieving a sessio
 
 _Recording tests:_
 
-![](<../../../.gitbook/assets/session-record-tests (1) (1) (1) (1) (1).png>)
+![](<../../../.gitbook/assets/session-record-tests (1) (1) (1) (1).png>)
 
 _Subsetting and recording tests:_
 
-![](<../../../.gitbook/assets/session-subset-record-tests (1) (1) (1) (1) (1).png>)
+![](<../../../.gitbook/assets/session-subset-record-tests (1) (1) (1) (1) (1) (1) (1).png>)
 
 This ensures that `launchable subset` and `launchable record tests` commands are 'linked', which is important for proper instrumentation.
 
@@ -28,13 +28,13 @@ Sometimes, the build, test, and reporting steps are split between different mach
 
 This can cause an extra session to be created, because `launchable record tests` doesn't find the session created by `launchable subset`:
 
-![](<../../../.gitbook/assets/duplicate-sessions (1) (1) (1) (1).png>)
+![](<../../../.gitbook/assets/duplicate-sessions (1) (1) (1) (1) (1).png>)
 
 ### Reused sessions
 
 Or, if the reporting machine is reused and persistent, the saved session from a previous `launchable record tests` invocation may be accidentally reused, combining tests from different sessions against the same build:
 
-![](<../../../.gitbook/assets/reused-session (1) (1) (1) (1) (1) (1).png>)
+![](<../../../.gitbook/assets/reused-session (1) (1) (1) (1) (1) (2).png>)
 
 ### Solution
 

diff --git a/...with-the-launchable-cli/use-flavors-to-run-the-best-tests-for-an-environment.md b/...with-the-launchable-cli/use-flavors-to-run-the-best-tests-for-an-environment.md
@@ -16,7 +16,7 @@ In these scenarios, a test result is not just a test result: it is the combinati
 
 Launchable supports these scenarios with a concept called **flavors**.
 
-![](<../../../.gitbook/assets/flavors-2x (1) (1) (1) (1).png>)
+![](<../../../.gitbook/assets/flavors-2x (1) (1) (1) (1) (1).png>)
 
 When you submit test results using `launchable record tests`, you can submit additional metadata in the form of key-value pairs using the `--flavor` option.