docs: Optimize GIFs and Screenshots (#3845)

Optimize GIFs and Screenshots
kubeshop · May 10, 2024 · f5d7cb6 · f5d7cb6
1 parent 0527ea4
commit f5d7cb6
Show file tree

Hide file tree

Showing 11 changed files with 7 additions and 7 deletions.
diff --git a/docs/docs/concepts/run-groups.md b/docs/docs/concepts/run-groups.md
@@ -36,7 +36,7 @@ The way to use run groups from the CLI is by running multiple folders at once:
 
 ![Run Groups CLI](../img/run-groups-cli.png)
 
-![Run Groups CLI 2](../img/run-groups-cli-2.png)
+![Run Groups CLI 2](../img/run-groups-cli-2.jpg)
 
 Users can also manually wait for a run group to be done from the CLI.
 

diff --git a/docs/docs/img/run-groups-cli-2.jpg b/docs/docs/img/run-groups-cli-2.jpg
diff --git a/docs/docs/tools-and-integrations/artillery-engine.mdx b/docs/docs/tools-and-integrations/artillery-engine.mdx
@@ -380,7 +380,7 @@ Most of the tests will fail as the import Pokemon flow reads from memory if the
 
 After running the initial set of tests, you can click the run link for any of them, update the assertions, and run the scripts once more. This flow enables complete a trace-based TDD flow.
 
-![assertions](./img/tracetest-cloud-typescript.gif)
+![assertions](./img/tracetest-cloud-typescript-resize.gif)
 
 ## Learn More
 

diff --git a/docs/docs/tools-and-integrations/artillery-plugin.mdx b/docs/docs/tools-and-integrations/artillery-plugin.mdx
@@ -430,7 +430,7 @@ Most of the tests will fail as the import Pokemon flow reads from memory if the
 
 After running the initial set of tests, you can click the run link for any of them, update the assertions, and run the scripts once more. This flow enables complete a trace-based TDD flow.
 
-![assertions](./img/tracetest-cloud-typescript.gif)
+![assertions](./img/tracetest-cloud-typescript-resize.gif)
 
 ## Learn More
 

diff --git a/docs/docs/tools-and-integrations/img/testkube-resize.gif b/docs/docs/tools-and-integrations/img/testkube-resize.gif
diff --git a/docs/docs/tools-and-integrations/img/tracetest-cloud-k6-resize.gif b/docs/docs/tools-and-integrations/img/tracetest-cloud-k6-resize.gif
diff --git a/docs/docs/tools-and-integrations/img/tracetest-cloud-typescript-resize.gif b/docs/docs/tools-and-integrations/img/tracetest-cloud-typescript-resize.gif
diff --git a/docs/docs/tools-and-integrations/img/tracetest-resize.gif b/docs/docs/tools-and-integrations/img/tracetest-resize.gif
diff --git a/docs/docs/tools-and-integrations/k6.mdx b/docs/docs/tools-and-integrations/k6.mdx
@@ -318,7 +318,7 @@ ERRO[0010] a panic occurred during JS execution: Tracetest: 5 jobs failed
 
 After running the initial set of tests, you can click the run link for any of them, update the assertions and run the scripts once more. This flow enables complete a trace-based TDD flow.
 
-![assertions](./img/tracetest-cloud-k6.gif)
+![assertions](./img/tracetest-cloud-k6-resize.gif)
 
 ## Learn More
 

diff --git a/docs/docs/tools-and-integrations/testkube.mdx b/docs/docs/tools-and-integrations/testkube.mdx
@@ -183,11 +183,11 @@ Finally, you can see the Tracetest results in your CLI:
 
 You can click the run link to open the test run in the Tracetest app. From there you can explore the generated trace, update the assertions and get the test definition to execute your test once more.
 
-![tracetest](./img/tracetest.gif)
+![tracetest](./img/tracetest-resize.gif)
 
 You can also explore the test execution from the Testkube dashboard.
 
-![testkube](./img/testkube.gif)
+![testkube](./img/testkube-resize.gif)
 
 ## What's Next?
 

diff --git a/docs/docs/tools-and-integrations/typescript.mdx b/docs/docs/tools-and-integrations/typescript.mdx
@@ -345,7 +345,7 @@ The output from the TypeScript script should be visible in the log for the `trac
 
 After running the initial set of tests, you can click the run link for any of them, update the assertions, and run the scripts once more. This flow enables complete a trace-based TDD flow.
 
-![assertions](./img/tracetest-cloud-typescript.gif)
+![assertions](./img/tracetest-cloud-typescript-resize.gif)
 
 ## Learn More