T: rename runner to dev-test
This commit is contained in:
1 parent
6dade6239d
commit
b476ac2b0c
6 files changed
+331
-219
No files matched your search
@@ -3,27 +3,27 @@
|
||||
The peers acceptance test is a NixOS VM test. Three machines run the real `slinuxm`: `alpha` and `beta` consolidate each other over plain HTTP, and `alpha` also declares the TLS-only `gamma` with a private CA. It needs KVM and takes minutes.
|
||||
|
||||
```sh
|
||||
devenv shell -- test vm peers # nix build .#tests.x86_64-linux.peers -L
|
||||
devenv shell -- dev-test vm peers # nix build .#tests.x86_64-linux.peers -L
|
||||
```
|
||||
|
||||
Against a tree without the consolidator the test stops at the first peers assertion; that is expected, the test is written ahead of the feature. `dev/test.nu` is the repository's test runner. `devenv shell -- test --help` lists its subcommands and the command behind each. Inside an interactive bash or zsh, `test` is the shell builtin, so `test vm` exits 0 without running anything. Use `devenv shell -- test …` or `nu dev/test.nu …`.
|
||||
Against a tree without the consolidator the test stops at the first peers assertion; that is expected, the test is written ahead of the feature. `dev/dev-test.nu` is the repository's test runner. `devenv shell -- dev-test --help` lists its subcommands and the command behind each. In an interactive `devenv shell`, `dev-test …` is that same script.
|
||||
|
||||
In Nushell the runner is a module. Load it once, for example in `config.nu`, and `test unit`, `test vm peers`, ... complete natively. Integration-test name completion is cached in `target/skyg-test-filters.cache`, keyed on the newest mtime of the Rust sources and the Cargo manifests.
|
||||
In Nushell the runner is a module. Load it once, for example in `config.nu`, and `dev-test unit`, `dev-test vm peers`, ... complete natively. Integration-test name completion is cached in `target/skyg-test-filters.cache`, keyed on the newest mtime of the Rust sources and the Cargo manifests.
|
||||
|
||||
```nu
|
||||
use /home/you/src/skyg-linux-tracker/dev/test.nu * # absolute path to dev/test.nu
|
||||
use /home/you/src/skyg-linux-tracker/dev/dev-test.nu * # absolute path to dev/dev-test.nu
|
||||
```
|
||||
|
||||
zsh and bash completion comes from the same command table. The generated script defines a `test` function for known subcommands (`test unit`, `test vm peers`, ...) and leaves other invocations (`test -f`) to the builtin. An interactive `devenv shell` sources the bash script and prints a one-line note on stderr. That hook runs in bash, so it cannot install zsh functions, and direnv will not carry them either. zsh users add the following to `.zshrc` after `compinit`:
|
||||
zsh and bash completion comes from the same command table. The generated script only registers completion for the external command `dev-test`. An interactive `devenv shell` sources the bash script. That hook runs in bash and direnv will not source it either, so zsh users add the following to `.zshrc` after `compinit`:
|
||||
|
||||
```sh
|
||||
source <(nu /home/you/src/skyg-linux-tracker/dev/test.nu completions zsh)
|
||||
source <(nu /home/you/src/skyg-linux-tracker/dev/dev-test.nu completions zsh)
|
||||
```
|
||||
|
||||
bash, from the repo checkout:
|
||||
|
||||
```sh
|
||||
source <(nu dev/test.nu completions bash)
|
||||
source <(nu dev/dev-test.nu completions bash)
|
||||
```
|
||||
|
||||
`nu dev/test.nu self-check` fails if the command table, the defined subcommands, the help text, the cargo argv, the filter cache or the shell wrapper drift apart.
|
||||
`nu dev/dev-test.nu self-check` fails if the command table, the defined subcommands, the help text, the cargo argv, the filter cache or the shell completion drift apart.
|
||||
Reference in new issue
Block a user