Resolved merge issues

keploy · Aug 19, 2024 · 475344d · 475344d
1 parent f19b77d
commit 475344d
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 10 deletions.
diff --git a/versioned_docs/version-2.0.0/quickstart/java-spring-postgres.md b/versioned_docs/version-2.0.0/quickstart/java-spring-postgres.md
@@ -112,7 +112,7 @@ keploy record -c "java -jar target/spring-petclinic-rest-3.0.2.jar"
 
 Now you can start interacting with the UI and Keploy will automatically create the testcases and mocks for it in a folder named 'keploy'.
 
-![Test Record](/static/img/pet-clinic-record.png)
+![Test Record](/img/pet-clinic-record.png)
 
 
 ### Running the testcases using Keploy
@@ -142,8 +142,8 @@ keploy record -c "docker compose up" --container-name javaApp --build-delay 100
 ```bash
 keploy test -c "docker compose up" --container-name javaApp --build-delay 50 --delay 20
 ```
-![Test Record](/static/img/pet-clinic-test1.png)
-![Test Record](/static/img/pet-clinic-test2.png)
+![Test Record](/img/pet-clinic-test1.png)
+![Test Record](/img/pet-clinic-test2.png)
 
 
 Here `delay` is the time it takes for your application to get started, after which Keploy will start running the testcases. If your application takes longer than 10s to get started, you can change the `delay` accordingly.

diff --git a/versioned_docs/version-2.0.0/quickstart/sample-ts.md b/versioned_docs/version-2.0.0/quickstart/sample-ts.md
@@ -73,7 +73,7 @@ sudo -E env "PATH=$PATH" keploy record -c 'ts-node src/app.ts'
 
 `-c 'ts-node src/app.ts`': Specifies the command to start your application (in this case, using ts-node to execute the TypeScript application entry point).
 
-![Test Record](../../../static/img/wsl-record-ts.png)
+![Test Record](/img/wsl-record-ts.png)
 
 ### Generating the test cases
 
@@ -195,8 +195,8 @@ Voila!! Our test cases have passed 🌟
 
 You will be able to see the summary of your test cases run in your terminal!
 
-![Test Record](../../../static/img/wsl-test-ts.png)
-![Test Record](../../../static/img/wsl-test-summary-ts.png)
+![Test Record](/img/wsl-test-ts.png)
+![Test Record](/img/wsl-test-summary-ts.png)
 
 
 Now its time for you to experiment further with different API calls and tweak the responses accordingly!
@@ -266,8 +266,8 @@ keploy test -c 'sudo docker-compose up' --containerName "ts-nhost" --delay 10
 ```
 This is what your response should look like!
 
-![Test Record](/static/img/wsl-test-ts.png)
-![Test Record](/static/img/wsl-test-summary-ts.png)
+![Test Record](/img/wsl-test-ts.png)
+![Test Record](/img/wsl-test-summary-ts.png)
 
 
 ## Wrapping it up 🎉

diff --git a/versioned_docs/version-2.0.0/quickstart/sanic-mongo.md b/versioned_docs/version-2.0.0/quickstart/sanic-mongo.md
@@ -66,7 +66,7 @@ keploy record -c "python3 server.py"
 ```
 You should be able to see this in your terminal
 
-![Test Record](/static/img/sanic-mongo-record.png)
+![Test Record](/img/sanic-mongo-record.png)
 
 <!-- <img src='/docs/static/img/sanic-mongo-record.png' alt="Test Record"  width="80%"/> -->
 
@@ -156,6 +156,6 @@ spec:
 ```
 This is how your terminal would look like :
 
-![Test Record](/static/img/sanic-mongo-test.png)
+![Test Record](/img/sanic-mongo-test.png)
 
 You can experiment with different API calls, modify the database response in mocks.yml, or adjust the request or response in test-x.yml. Then, run the tests again to see the change in response