@@ -22,20 +22,20 @@ You can run tests normally with `go test`.
22
22
You'll need the [ Autobahn Test suite pip package] ( https://github.com/crossbario/autobahn-testsuite ) .
23
23
In the future this dependency will be removed. See [ #117 ] ( https://github.com/nhooyr/websocket/issues/117 ) .
24
24
25
- On submission please check if CI has passed and if not, please correct your code such that it does.
26
- If necessary, you may run CI locally with the ` ci/run.sh ` script which will fmt, lint and test your code
27
- with coverage.
28
- You'll need [ shellcheck] ( https://github.com/koalaman/shellcheck#installing ) , node and the
29
- Autobahn Test suite linked above.
25
+ Please ensure CI passes for your changes. If necessary, you may run CI locally. The various steps are located
26
+ in ` ci/*.sh ` .
30
27
31
- For coverage details locally, please see ` ci/out/coverage.html ` after running ` ci/run.sh ` or ` ci/test.sh ` .
32
- For remote coverage, you can use either [ codecov] ( https://codecov.io/gh/nhooyr/websocket ) or download the
33
- ` coverage.html ` artifact on the test step in CI.
28
+ ` ci/fmt.sh ` requires node (specifically prettier).
29
+ ` ci/lint.sh ` requires [ shellcheck] ( https://github.com/koalaman/shellcheck#installing ) .
30
+ ` ci/test.sh ` requires the [ Autobahn Test suite pip package] ( https://github.com/crossbario/autobahn-testsuite ) .
31
+ ` ci/bench.sh ` requires only Go.
32
+ ` ci/run.sh ` runs everything in the above order and requires all of their dependencies.
34
33
35
- You can also run any of the CI steps individually. All of them are scripts in the ` ci ` directory .
34
+ See [ ../ci/image/Dockerfile ] ( ../ci/image/Dockerfile ) for the installation of the CI dependencies on ubuntu .
36
35
37
- See [ ../ci/image/Dockerfile] ( ../ci/image/Dockerfile ) for the
38
- installation of the CI dependencies on arch linux.
36
+ For CI coverage, you can use either [ codecov] ( https://codecov.io/gh/nhooyr/websocket ) or click the
37
+ ` coverage.html ` artifact on the test step in CI.
38
+ For coverage details locally, please see ` ci/out/coverage.html ` after running ` ci/run.sh ` or ` ci/test.sh ` .
39
39
40
- You can benchmark the library with ` ./ci/benchmark. sh` . You only need Go to run that script.
41
- Benchmark profiles generated by that script are also available as artifacts on the bench step .
40
+ Benchmark profiles generated by ` bench. sh` are available as artifacts on the bench step so that they
41
+ may be analyzed .
0 commit comments