extern/nushell
1
0
Fork 1
mirror of https://github.com/nushell/nushell.git synced 2024-11-26 18:33:50 +01:00
Code Issues Packages Projects Releases Wiki Activity
0567407f85
nushell/crates
History
Antoine Stevan 0567407f85
standard library: bring the tests into the main CI (#8525) 
Should close one of the tasks in #8450.

# Description
> **Note**
> in order of appearance in the global diff

- 1b7497c419 adds the `std-tests` job to
the CI which
  1. installs `nushell` in the runner
  2. run the `tests.nu` module
> see `open .github/workflows/ci.yml | get jobs.std-tests | to yaml`

-
[`ec85b6fd`..`9c122115`](ec85b6fd3fc004cd94e3fada5c8e5fe2714fd629..9c12211564ca8ee90ed65ae45776dccb8f8e4ef1)
is where all the magic happens => see below
- 🧪 799c7eb7fd introduces some
bugs and failing test to see how the CI behaves => see how the [tests
failed](https://github.com/nushell/nushell/actions/runs/4460098237/jobs/7833018256)
as expected ❌
- 🧪 and c3de1fafb5 reverts the
failing tests, i.e. the previous commit, leaving a standard library
whose tests all pass 🎉 => see the [tests
passing](https://github.com/nushell/nushell/actions/runs/4460153434/jobs/7833110719?pr=8525#step:5:1)
now ✔️

## the changes to the runner
> see
[`ec85b6fd`..`9c122115`](ec85b6fd3fc004cd94e3fada5c8e5fe2714fd629..9c12211564ca8ee90ed65ae45776dccb8f8e4ef1)

the issue with the previous runner was the following: the clever trick
of using `nu -c "use ...; test"` did print the errors when occuring but
they did not capture the true "failure", i.e. in all cases the
`$env.LAST_EXIT_CODE` was set to `0`, never stopping the CI when a test
failed 🤔

i first tried to `try` / `catch` the error in
ec85b6fd3f which kinda worked but only
throw a single error, the first one

i thought it was not the best and started thinking about a solution to
have a complete report of all failing tests, at once, to avoid running
the CI multiple times!

the easiest solution i found was the one i implemented in
9c12211564
> **Warning**
> this changes the structure of the runner quite a bit, but the `for`
loops where annoying to manipulate structured data and allow the runner
to draw a complete report...

now the runner does the following
- compute the list of all available tests in a table with the `file`,
`module` and `name` columns (first part of the pipe until `flatten` and
`rename`)
- run the tests one by one computing the new `pass` column
  - with a `log info`
- captures the failing ones => puts `true` in `pass` if the test passes,
`false` otherwise
- if at least one test has failed, throw a single error with the list of
failing tests

### hope you'll like it 😌 

# User-Facing Changes
```
$nothing
```

# Tests + Formatting
the standard tests now return a true error that will stop the CI

# After Submitting
```
$nothing
```
2023-03-25 19:29:08 +01:00
..
nu_plugin_custom_values bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu_plugin_example bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu_plugin_formats bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu_plugin_gstat bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu_plugin_inc bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu_plugin_python update nu_plugin_python due to signature changes (#8107) 2023-02-18 13:27:24 +00:00
nu_plugin_query bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu-cli Clean up unnecessary macro use (#8607) 2023-03-25 20:17:20 +13:00
nu-cmd-lang Speed up tight loop benchmarks (#8609) 2023-03-26 06:12:57 +13:00
nu-color-config Clean up unnecessary macro use (#8607) 2023-03-25 20:17:20 +13:00
nu-command Speed up tight loop benchmarks (#8609) 2023-03-26 06:12:57 +13:00
nu-engine Move variables to var stack (#8604) 2023-03-25 12:56:45 +13:00
nu-explore Clean up unnecessary macro use (#8607) 2023-03-25 20:17:20 +13:00
nu-glob bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu-json bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu-parser type-check default values of list annotations (#8600) 2023-03-25 08:57:18 +13:00
nu-path bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu-plugin bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu-pretty-hex bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu-protocol Speed up tight loop benchmarks (#8609) 2023-03-26 06:12:57 +13:00
nu-system bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu-table bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu-term-grid bump to 0.77.2 (#8496) 2023-03-17 21:29:15 +13:00
nu-test-support Remove once_cell dependency from nu-test-support create. (#8568) 2023-03-22 19:36:52 +01:00
nu-utils standard library: bring the tests into the main CI (#8525) 2023-03-25 19:29:08 +01:00
README.md Remove old nushell/merge engine-q 2022-02-07 14:54:06 -05:00

README.md

Nushell core libraries and plugins

These sub-crates form both the foundation for Nu and a set of plugins which extend Nu with additional functionality.

Foundational libraries are split into two kinds of crates:

  • Core crates - those crates that work together to build the Nushell language engine
  • Support crates - a set of crates that support the engine with additional features like JSON support, ANSI support, and more.

Plugins are likewise also split into two types:

  • Core plugins - plugins that provide part of the default experience of Nu, including access to the system properties, processes, and web-connectivity features.
  • Extra plugins - these plugins run a wide range of different capabilities like working with different file types, charting, viewing binary data, and more.