Skip to content

Commit 00f15ad

Browse files
committed
Tune README
1 parent d06f45d commit 00f15ad

1 file changed

Lines changed: 1 addition & 11 deletions

File tree

README.md

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -125,8 +125,6 @@ use the bundled `docker/ut-run-tests` launcher.
125125
/path/to/UnitTesting/docker/ut-run-tests . --file tests/test_example.py
126126
```
127127

128-
(Use `docker/ut-run-tests.cmd` in cmd.exe/PowerShell.)
129-
130128
If `UnitTesting/docker` is on your `PATH`, you can simply run:
131129

132130
```sh
@@ -137,23 +135,15 @@ This launcher calls `docker/run_tests.py`, which runs tests in a Docker
137135
container (headless), streams output to stdout/stderr and keeps a cache
138136
volume so repeated runs are fast.
139137

140-
By default it:
141-
142-
- builds `unittesting-local` image from `./docker` if missing
143-
- mounts your repo as `/project`
144-
- runs UnitTesting through the same CI shell entrypoints
145-
- stores Sublime install/cache in docker volume `unittesting-home`
146-
- synchronizes only changed files into `Packages/<Package>` using `rsync`
147-
148138
Useful options:
149139

150140
- `--file tests/test_foo.py`
151141
- `--pattern test_foo.py --tests-dir tests/subdir`
152142
- `--coverage`
153143
- `--failfast`
154144
- `--reload-package-on-testing` (default: off)
155-
- `--dry-run` (only print runtime metadata and schedule)
156145
- `--scheduler-delay-ms 0` (default)
146+
- `--dry-run` (only print runtime metadata and schedule)
157147
- `--refresh-cache` (re-bootstrap cached `/root` state)
158148
- `--refresh-image` (rebuild local Docker image)
159149
- `--refresh` (both cache and image refresh)

0 commit comments

Comments
 (0)