the tests of the existing library are broken, let me fix them and i'll come back to this PR right after the changes have been applied 😉

• see standard library: fix the tests for the new closure parsing of 0.77.2 #8504 for the fix 👍

in the meantime, to help the developer trying to run the new tests runner, i think a --list option to list all the modules and their respective available commands would be very nice 😮

and also allowing to pass multiple modules and commands maybe?
not sure how easy that would be though 🤔

I was thinking about --dry-run or --dry. I think it describes better what it does. And as I remember, other thest suites uses something similar. Do you prefer --list instead?

At first step I do not want implement support for multiple modules & commands. I can be useful, but until somebody really needs it for me it seems to me L'art pour L'art work. (Also can be workarounded easily with chained commands.)

I was thinking about --dry-run or --dry. I think it describes better what it does. And as I remember, other thest suites uses something similar. Do you prefer --list instead?

i would say --list is more nushelly 😋
and to me, it represents more what it does, i.e. listing available options 👍

so i'd personnally push --list forward.

At first step I do not want implement support for multiple modules & commands. I can be useful, but until somebody really needs it for me it seems to me L'art pour L'art work. (Also can be workarounded easily with chained commands.)

yeah you got a point, never mind about that one 😉

something like this, right? 😏

def "multi-test" [] {
    let tests = $in

    let runner = (
        git rev-parse --show-toplevel
        | str trim
        | path join "crates" "nu-utils" "standard_library" "tests.nu"
    )

    $tests
    | transpose module command
    | flatten
    | each {|test|
        nu $runner --module $test.module --command $test.command
    }
}

{foo: [f1 f2 f3], bar: [b1 b4]} | multi-test

That can be an example. The other one is just nu tests.nu --module test_a; nu tests.nu --module test_b. I think it is rarely needed. The typical use case is to run just a given command for TDD, or run the tests for my currently developed module.

I added --list option.

Conflict with main branch is resolved.

It seems that there is an unrelated fail in Ubuntu 20.04 checks.

Master is merged to get rid of CI errors.

Codecov Report

Merging #8499 (2912b24) into main (ecc153c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #8499   +/-   ##
=======================================
  Coverage   68.51%   68.51%           
=======================================
  Files         624      624           
  Lines      100562   100562           
=======================================
  Hits        68903    68903           
  Misses      31659    31659           

Then let's give this a shot! Thanks!