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
+43
Original file line number
Diff line number
Diff line change
@@ -221,6 +221,49 @@ The Python interpreter output will look like below.
221
221
>>>
222
222
```
223
223
224
+
### Testing
225
+
You can run integration and unit tests in interactive mode of IDEorin terminal mode using the command:
226
+
```bash
227
+
pytest tests/integration_tests
228
+
pytest tests/unit_tests
229
+
```
230
+
231
+
#### E2E tests have 2 options for launching (legacy runner):
232
+
- using a compiler based on the substrait code
233
+
- using an already built docker image (docker runner)
234
+
235
+
#### Using `docker runner` (default for now):
236
+
-E2E tests with docker image do not require preliminary compilation
237
+
- are executed very quickly
238
+
- require docker installed inOS
239
+
240
+
Ho to use:
241
+
```bash
242
+
pytest tests/e2e_tests
243
+
```
244
+
245
+
#### TUsing `legacy runner`:
246
+
- Will start compilation of the collected code in your subtensor repository
247
+
- you must provide the `LOCALNET_SH_PATH` variable in the local environment with the path to the file`/scripts/localnet.sh`in the cloned repository within your OS
248
+
- you can use the `BUILD_BINARY=0` variable, this will skip the copy step for each test.
249
+
- you can use the `USE_DOCKER=0` variable, this will run tests using the "legacy runner", even if docker is installed in your OS
0 commit comments