nushell/crates/nu-std/tests/logger_tests/test_basic_commands.nu
Yethal 9ef1203ef9
Implement annotations support in test runner (#9406)
<!--
if this PR closes one or more issues, you can automatically link the PR
with
them by using one of the [*linking
keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword),
e.g.
- this PR should close #xxxx
- fixes #xxxx

you can also mention related issues, PRs or discussions!
-->

# Description
Test runner now uses annotations instead of magic function names to pick
up code to run. Additionally skipping tests is now done on annotation
level so skipping and unskipping a test no longer requires changes to
the test code

In order for a function to be picked up by the test runner it needs to
meet following criteria:
* Needs to be private (all exported functions are ignored)
* Needs to contain one of valid annotations (and only the annotation)
directly above the definition, all other comments are ignored

Following are considered valid annotations:
* \# test
* \# test-skip
* \# before-all
* \# before-each
* \# after-each
* \# after-all

# User-Facing Changes
<!-- List of all changes that impact the user experience here. This
helps us keep track of breaking changes. -->

# Tests + Formatting
<!--
Don't forget to add tests that cover your changes.

Make sure you've run and fixed any issues with these commands:

- `cargo fmt --all -- --check` to check standard code formatting (`cargo
fmt --all` applies these changes)
- `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A
clippy::needless_collect -A clippy::result_large_err` to check that
you're using the standard code style
- `cargo test --workspace` to check that all tests pass
- `cargo run -- crates/nu-std/tests/run.nu` to run the tests for the
standard library

> **Note**
> from `nushell` you can also use the `toolkit` as follows
> ```bash
> use toolkit.nu # or use an `env_change` hook to activate it
automatically
> toolkit check pr
> ```
-->

# After Submitting
<!-- If your PR had any user-facing changes, update [the
documentation](https://github.com/nushell/nushell.github.io) after the
PR is merged, if necessary. This will help us keep the docs up to date.
-->
2023-07-02 10:41:33 +02:00

98 lines
1.9 KiB
Text

use std *
def run [
system_level,
message_level
--short
] {
do {
if $short {
^$nu.current-exe --commands $'use std; NU_LOG_LEVEL=($system_level) std log ($message_level) --short "test message"'
} else {
^$nu.current-exe --commands $'use std; NU_LOG_LEVEL=($system_level) std log ($message_level) "test message"'
}
} | complete | get --ignore-errors stderr
}
def "assert no message" [
system_level,
message_level
] {
let output = (run $system_level $message_level)
assert equal "" $output
}
def "assert message" [
system_level,
message_level,
message_level_str
] {
let output = (run $system_level $message_level)
assert str contains $output $message_level_str
assert str contains $output "test message"
}
def "assert message short" [
system_level,
message_level,
message_level_str
] {
let output = (run --short $system_level $message_level)
assert str contains $output $message_level_str
assert str contains $output "test message"
}
#[test]
def critical [] {
assert no message 99 critical
assert message CRITICAL critical CRT
}
#[test]
def critical_short [] {
assert message short CRITICAL critical C
}
#[test]
def error [] {
assert no message CRITICAL error
assert message ERROR error ERR
}
#[test]
def error_short [] {
assert message short ERROR error E
}
#[test]
def warning [] {
assert no message ERROR warning
assert message WARNING warning WRN
}
#[test]
def warning_short [] {
assert message short WARNING warning W
}
#[test]
def info [] {
assert no message WARNING info
assert message INFO info "INF" # INF has to be quoted, otherwise it is the `inf` float
}
#[test]
def info_short [] {
assert message short INFO info I
}
#[test]
def debug [] {
assert no message INFO debug
assert message DEBUG debug DBG
}
#[test]
def debug_short [] {
assert message short DEBUG debug D
}