Updated Development (markdown)
@ -35,7 +35,7 @@ The tests run against actual zfs commands and create a lot of temporary pools vi
|
||||
|
||||
The tests also need ssh support via root@localhost, so it will create and install a sshkey if needed.
|
||||
|
||||
## Running the whole suite
|
||||
### Running the whole suite
|
||||
|
||||
This takes a few minutes and is also done automaticly on each commit via github actions: https://github.com/psy0rz/zfs_autobackup/actions
|
||||
|
||||
@ -53,7 +53,7 @@ test piped exitcodes ... ok
|
||||
...
|
||||
```
|
||||
|
||||
## Running one test
|
||||
### Running one test
|
||||
|
||||
Since running the whole suite takes long, you can run one test like this:
|
||||
|
||||
@ -68,7 +68,7 @@ Since running the whole suite takes long, you can run one test like this:
|
||||
test_verify (test_verify.TestZfsEncryption) ... Preparing zfs filesystems...
|
||||
```
|
||||
|
||||
## Automaticly run test on save
|
||||
### Automaticly run test on save
|
||||
|
||||
I use `entr` for this:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user