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
Copy file name to clipboardExpand all lines: README.md
+12-3Lines changed: 12 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -159,7 +159,7 @@ yarn test:unit
159
159
Note that the parachain needs to be running for all tests to run.
160
160
161
161
```bash
162
-
docker-compose up
162
+
docker-compose up -d
163
163
```
164
164
165
165
The default parachain runtime is Kintsugi.
@@ -178,9 +178,18 @@ yarn test
178
178
yarn test:integration
179
179
```
180
180
181
-
NOTE: While the parachain is starting up, there will be warnings from the integration tests until it can locate the locally running test vaults. Expect the startup to take around 2-3 minutes, and only start the integration tests after that time frame.
181
+
NOTE: While the parachain is starting up, there will be warnings from the integration tests until it can locate the locally running test vaults. Expect the startup to take a few seconds, before the integration tests start.
182
182
183
-
Another option is to check the logs, i.e. for `vault_1` you can use this:
183
+
##### Dealing with timeouts during local testing
184
+
185
+
At times, when running tests locally, the timeout set in `package.json`'s `jest.testTimeout` setting might not be enough. In that case, you can override the `testTimeout` value (in ms) on the command line:
186
+
187
+
```bash
188
+
yarn test:integration --testTimeout=900000
189
+
```
190
+
191
+
##### Check service logs in detached mode
192
+
To check the logs or the services (for example, `vault_1`) you can use this:
0 commit comments