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
+9-3Lines changed: 9 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -234,23 +234,29 @@ pytest tests/unit_tests
234
234
- using a compiler based on the substrait code
235
235
- using an already built docker image (docker runner)
236
236
237
+
#### Local environment variables:
238
+
-`LOCALNET_SH_PATH`- path to `localnet.sh` script in cloned subtensor repository (for legacy runner);
239
+
-`BUILD_BINARY`- (`=0`or`=1`) - used with`LOCALNET_SH_PATH`for build ornot before start localnet node (for legacy runner);
240
+
-`USE_DOCKER`- (`=0`or`=1`) - used if you want to use specific runner to run e2e tests (for docker runner);
241
+
-`FAST_BLOCKS`- (`=0`or`=1`) - allows you to run a localnet node in fast or non-fast blocks mode (for both types of runers).
242
+
237
243
#### Using `docker runner` (default for now):
238
244
-E2E tests with docker image do not require preliminary compilation
239
245
- are executed very quickly
240
246
- require docker installed inOS
241
247
242
-
Ho to use:
248
+
How to use:
243
249
```bash
244
250
pytest tests/e2e_tests
245
251
```
246
252
247
-
#### TUsing `legacy runner`:
253
+
#### Using `legacy runner`:
248
254
- Will start compilation of the collected code in your subtensor repository
249
255
- 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
250
256
- you can use the `BUILD_BINARY=0` variable, this will skip the copy step for each test.
251
257
- 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