2023-03-20 14:57:28 +01:00
|
|
|
use std.nu *
|
|
|
|
|
|
|
|
export def test_assert [] {
|
|
|
|
assert true
|
|
|
|
assert (1 + 2 == 3)
|
|
|
|
assert error { assert false }
|
|
|
|
assert error { assert (1 + 2 == 4) }
|
|
|
|
}
|
|
|
|
|
|
|
|
export def test_assert_equal [] {
|
|
|
|
assert equal (1 + 2) 3
|
|
|
|
assert equal (0.1 + 0.2 | into string | into decimal) 0.3 # 0.30000000000000004 == 0.3
|
|
|
|
assert error { assert equal 1 "foo" }
|
Require that values that look like numbers parse as numberlike (#8635)
# Description
Require that any value that looks like it might be a number (starts with
a digit, or a '-' + digit, or a '+' + digits, or a special form float
like `-inf`, `inf`, or `NaN`) must now be treated as a number-like
value. Number-like syntax can only parse into number-like values.
Number-like values include: durations, ints, floats, ranges, filesizes,
binary data, etc.
# User-Facing Changes
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
Just making sure we see this for release notes 😅
This breaks any and all numberlike values that were treated as strings
before. Example, we used to allow `3,` as a bare word. Anything like
this would now require quotes or backticks to be treated as a string or
bare word, respectively.
# 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` to check that you're using the standard code
style
- `cargo test --workspace` to check that all tests pass
> **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-03-28 08:31:38 +02:00
|
|
|
assert error { assert equal (1 + 2) "4)" }
|
2023-03-20 14:57:28 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
export def test_assert_not_equal [] {
|
|
|
|
assert not equal (1 + 2) 4
|
|
|
|
assert not equal 1 "foo"
|
Require that values that look like numbers parse as numberlike (#8635)
# Description
Require that any value that looks like it might be a number (starts with
a digit, or a '-' + digit, or a '+' + digits, or a special form float
like `-inf`, `inf`, or `NaN`) must now be treated as a number-like
value. Number-like syntax can only parse into number-like values.
Number-like values include: durations, ints, floats, ranges, filesizes,
binary data, etc.
# User-Facing Changes
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
BREAKING CHANGE
Just making sure we see this for release notes 😅
This breaks any and all numberlike values that were treated as strings
before. Example, we used to allow `3,` as a bare word. Anything like
this would now require quotes or backticks to be treated as a string or
bare word, respectively.
# 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` to check that you're using the standard code
style
- `cargo test --workspace` to check that all tests pass
> **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-03-28 08:31:38 +02:00
|
|
|
assert not equal (1 + 2) "3)"
|
2023-03-20 14:57:28 +01:00
|
|
|
assert error { assert not equal 1 1 }
|
|
|
|
}
|
|
|
|
|
|
|
|
export def test_assert_error [] {
|
|
|
|
let failing_code = {|| missing_code_to_run}
|
|
|
|
assert error $failing_code
|
|
|
|
|
|
|
|
let good_code = {|| }
|
|
|
|
let assert_error_raised = (try { do assert $good_code; false } catch { true })
|
|
|
|
assert $assert_error_raised "The assert error should raise an error if there is no error in the executed code."
|
|
|
|
}
|
|
|
|
|
|
|
|
export def test_assert_less [] {
|
|
|
|
assert less 1 2
|
|
|
|
assert error { assert less 1 1 }
|
|
|
|
}
|
|
|
|
|
|
|
|
export def test_assert_less_or_equal [] {
|
|
|
|
assert less or equal 1 2
|
|
|
|
assert less or equal 1 1
|
|
|
|
assert error { assert less or equal 1 0 }
|
|
|
|
}
|
|
|
|
|
|
|
|
export def test_assert_greater [] {
|
|
|
|
assert greater 2 1
|
|
|
|
assert error { assert greater 2 2 }
|
|
|
|
}
|
|
|
|
|
|
|
|
export def test_assert_greater_or_equal [] {
|
|
|
|
assert greater or equal 1 1
|
|
|
|
assert greater or equal 2 1
|
|
|
|
assert error { assert greater or equal 0 1 }
|
|
|
|
}
|
|
|
|
|
|
|
|
export def test_assert_length [] {
|
|
|
|
assert length [0, 0, 0] 3
|
|
|
|
assert error { assert length [0, 0] 3 }
|
|
|
|
}
|
|
|
|
|
|
|
|
# export def test_assert_§ [] {
|
|
|
|
# assert §
|
|
|
|
# assert error { assert § }
|
|
|
|
# }
|
|
|
|
|