@@ -32,16 +32,15 @@ To contribute code to the project, open a [pull request][pulls].
32
32
Before you do that, please make sure the any new features is covered
33
33
by tests and that the tests pass.
34
34
35
- To run the tests, install and setup
36
- [ cask] , then run them with
35
+ To run the tests, install [ eldev] , and run the tests with:
37
36
``` bash
38
- make test
37
+ eldev test
39
38
```
40
39
41
40
Tests can also be run from inside Emacs,
42
41
using ` M-x ert-run-tests-interactively ` but when you do so, be aware
43
42
that there might be unexpected interaction with your Emacs
44
- configurations; Tests passing when run from Cask is what matters.
43
+ configurations; Tests passing when run from Eldev is what matters.
45
44
46
45
After you've sent your pull request, please check the result of
47
46
[ GitHub actions] [ actions ] running tests on your pull request. GitHub
@@ -54,7 +53,7 @@ For larger features, it's a good idea to first open an
54
53
thinking about working on it. This gives an opportunity to discuss the
55
54
new feature and its possible implementations.
56
55
57
- [ cask ] : https://github.com/szermatt/emacs-bash-completion/issues
56
+ [ eldev ] : https://emacs-eldev. github.io/eldev/
58
57
[ issues ] : https://github.com/szermatt/emacs-bash-completion/issues
59
58
[ actions ] : https://github.com/szermatt/emacs-bash-completion/actions
60
59
[ pulls ] : https://github.com/szermatt/emacs-bash-completion/pulls
0 commit comments