Skip to content

Commit 8297095

Browse files
fix: add delay to test mode in readme (#63)
* fix: updated the app to create tables everytime Signed-off-by: Pranshu Srivastava <[email protected]> * added delay Signed-off-by: Pranshu Srivastava <[email protected]> * explained delay Signed-off-by: Pranshu Srivastava <[email protected]> * formatted delay Signed-off-by: Pranshu Srivastava <[email protected]> --------- Signed-off-by: Pranshu Srivastava <[email protected]>
1 parent d083354 commit 8297095

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

spring-petclinic/README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
## Introduction
22

3-
This is a petclinic website where you can record testcases and mocks by interacting with the UI, and then test them using Keploy.
3+
This is a petclinic app where you can record testcases and mocks by interacting with the UI, and then test them using Keploy.
44
This project has two parts - the frontend and backend, since Keploy is a backend testing platform, we need to start the backend part of the project
55
using Keploy and run the frontend as it is.
66

@@ -47,13 +47,14 @@ mvn clean install -Dmaven.test.skip=true
4747
keploy record -c "java -jar target/<name-of-your-jar>"
4848
```
4949

50-
Now when you interact with the UI, the tests should start getting created in a folder called 'keploy' in the directory where you started the backend. When you are done recording the testcases and mocks, you can test them using keploy.
50+
Now when you interact with the UI, the tests should start getting created in a folder called 'keploy' in the directory where you started the backend. When you are done recording the testcases and mocks, you can run them using keploy.
5151

52-
## Testing the testcases using Keploy
52+
## Running the testcases using Keploy
5353

5454
```
55-
keploy test -c "java -jar target/<name-of-your-jar>"
55+
keploy test -c "java -jar target/<name-of-your-jar>" --delay 10
5656
```
57+
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.
5758

5859
Hope this helps you out, if you still have any questions, reach out to us on our [Slack](https://join.slack.com/t/keploy/shared_invite/zt-12rfbvc01-o54cOG0X1G6eVJTuI_orSA)
5960

0 commit comments

Comments
 (0)