T: docs: interactive dev-test lives inside devenv shell; module-mode notes
AGENTS.md said the same command works in an interactive shell, which only holds inside devenv shell or direnv (the script is on PATH there). docs/consolidator.md now says the filter cache sits at the repo root and that a failing check raises a catchable error instead of closing the session.
This commit is contained in:
1 parent
b01a409d35
commit
5edbd388d1
2 files changed
+2
-2
No files matched your search
@@ -8,7 +8,7 @@ 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/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 `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.
|
||||
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` at the repo root (not relative to the current directory, so completion works from any subdirectory), keyed on the newest mtime of the Rust sources and the Cargo manifests. A failing check raises a catchable error instead of exiting, so a red `dev-test unit` does not close the Nushell session that loaded the module; script mode still exits non-zero.
|
||||
|
||||
```nu
|
||||
use /home/you/src/skyg-linux-tracker/dev/dev-test.nu * # absolute path to dev/dev-test.nu
|
||||
|
||||
Reference in new issue
Block a user