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
2. Uncomment localhost addresses and comment the docker addresses for the services in the `peer-prep\src\backend\matching-service\config\config.js` file as below:
50
+
2. Uncomment localhost addresses and comment the docker addresses for the services in the `MatchingService\config\config.js` file as below:
@@ -233,13 +236,17 @@ Sample data for Question collection:
233
236
}
234
237
```
235
238
239
+
Note:
240
+
241
+
> For other test, please refer to the project report appendix.
242
+
236
243
237
244
#### Jest testing
238
245
239
246
1. Test the service using terminal commands:
240
247
241
248
```
242
-
cd peer-prep\src\backend\matching-service
249
+
cd MatchingService
243
250
npm test
244
251
```
245
252
@@ -248,23 +255,26 @@ npm test
248
255
249
256
**Note**:
250
257
251
-
> Please delete the containers for other microservices.
258
+
> Please ensure that there are no active container of the required services.
252
259
253
-
1. Navigate to peerprep directory.
260
+
1. Navigate to MatchingService directory.
254
261
255
-
2. Comment localhost addresses and uncomment the docker addresses for the service in the `peer-prep\src\backend\matching-service\config\config.js` file as below:
262
+
2. Comment localhost addresses and uncomment the docker addresses for the service in the `MatchingService\config\config.js` file as below, it sometimes use local addresses depend on different configuration of machine / docker:
0 commit comments