You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Remove standalone docker-compose up --build step
- Add clear instructions to stop containers before running tests
- Prevent port-in-use conflicts and make workflow clearer
- Ensure users stop services after test completion
- Build verified successfully with no errors
Signed-off-by: Nsanjayboruds <nishantborude555@gmail.com>
And once you are done, you can stop the recording and give yourself a pat on the back! With that simple spell, you've conjured up test cases with mocks! Explore the **keploy** directory and you'll discover your handiwork in the `tests` directory and `mocks.yml`.
137
120
121
+
### Stop the Running Services
122
+
123
+
```bash
124
+
docker-compose down
125
+
```
126
+
138
127
Want to see if everything works as expected?
139
128
140
129
### Run Tests 🧪
@@ -145,6 +134,12 @@ Time to put things to the test 🧪
145
134
keploy test -c "docker-compose up" --container-name "ruby-books-app" --delay 10
146
135
```
147
136
137
+
After tests complete, stop the services:
138
+
139
+
```bash
140
+
docker-compose down
141
+
```
142
+
148
143
> The `--delay` flag? Oh, that's just giving your app a little breather (in seconds) before the test cases come knocking.
149
144
150
145
Final thoughts? Dive deeper! Try different API calls, tweak the DB response in the `mocks.yml`, or fiddle with the request or response in `test-x.yml`. Run the tests again and see the magic unfold!✨👩💻👨💻✨
0 commit comments