Skip to content

Commit 4802e17

Browse files
committed
some touch up in README
1 parent c0f7f00 commit 4802e17

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

README.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,9 +12,9 @@ This is a unittest framework for Sublime Text. It runs unittest testcases on loc
1212

1313
## Sublime Text 4
1414

15-
Sublime Text 4 is now supported.
16-
- As Package Control has not yet support python 3.8, `coverage` on Python 3.8 packages are not working now.
17-
- Only local testing is possible and CI services are also not available now.
15+
Sublime Text 4 is now supported (with some caveats)
16+
- Running `coverage` on Python 3.8 packages is not working now.
17+
- Only local testing is supported now (CI services are not working).
1818

1919
## Preparation
2020

@@ -172,7 +172,7 @@ asynchronous codes.
172172
173173
An example would be found in [here](https://github.com/randy3k/UnitTesting-example/tree/deferred).
174174
175-
To activate deferred testing on Travis CI and AppVeyor, put the following line in
175+
To activate deferred testing, put the following line in
176176
`unittesting.json`.
177177
178178
```
@@ -210,7 +210,7 @@ example would be found in
210210
[here](https://github.com/randy3k/UnitTesting-example/tree/async).
211211
212212
However, it is known that async test does not work very well with coverage.
213-
In general, it is recommended to use deferred testing over async testing since there is
213+
In general, it is **recommended** to use deferred testing over async testing since there is
214214
no need to worry about race condition.
215215
216216

0 commit comments

Comments
 (0)