chore: rename nu-test instances to nutest to be consistent with the command names

Author: vyadh

.github/workflows/tests.yaml

@@ -36,7 +36,7 @@ jobs:
         with:
           version: ${{ matrix.version }}
 
-      - name: Test Nu-Test
+      - name: Test Nutest
         shell: nu {0}
         run: |
           nu -c 'use nutest; (

PLAN.md

@@ -11,7 +11,6 @@
 
 ## Milestone: Version 1.0
 
-- Use step outputs for file references
 - Versioning strategy, labels and docs/automation
 - Basic contributor agreement if needed
 
@@ -29,6 +28,7 @@
 ## Future Ideas
 
 - Support matchers in `list-tests` (a trivial win)
+- Allow before-all and before-each to be specified without returning context
 - Optimisation: If nothing requires test output (e.g. summary), we can avoid having to process it
 - Optionally write decoded event stream to file to help debug Nutest itself.
 - Optionally allow running ignored tests.

README.md

@@ -1,18 +1,18 @@
-# Nu-test
+# Nutest
 
-![CI/CD](https://github.com/vyadh/nu-test/actions/workflows/tests.yaml/badge.svg)
+![CI/CD](https://github.com/vyadh/nutest/actions/workflows/tests.yaml/badge.svg)
 ![Tests](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fgist.githubusercontent.com%2Fvyadh%2F0cbdca67f966d7ea2e6e1eaf7c9083a3%2Fraw%2Ftest-summary.json&query=%24.total&label=Tests)
 ![Passed](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fgist.githubusercontent.com%2Fvyadh%2F0cbdca67f966d7ea2e6e1eaf7c9083a3%2Fraw%2Ftest-summary.json&query=%24.passed&label=Passed&color=%2331c654)
 ![Failed](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fgist.githubusercontent.com%2Fvyadh%2F0cbdca67f966d7ea2e6e1eaf7c9083a3%2Fraw%2Ftest-summary.json&query=%24.failed&label=Failed&color=red)
 ![Skipped](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fgist.githubusercontent.com%2Fvyadh%2F0cbdca67f966d7ea2e6e1eaf7c9083a3%2Fraw%2Ftest-summary.json&query=%24.skipped&label=Skipped&color=yellow)
 
-A [Nushell](https://www.nushell.sh) test runner.
+A [Nushell](https://www.nushell.sh) test framework.
 
-![An example nu-test run](resources/test-run.png)
+![An example nutest run](resources/test-run.png)
 
 *^ Tests are structured data that can be processed just like any other table.*
 
-![An example nu-test run](resources/test-run-terminal.png)
+![An example nutest run](resources/test-run-terminal.png)
 
 *^ Terminal mode - test results appear as they complete.*
 
@@ -36,8 +36,8 @@ Note: Nu-test is fully functional but currently still in pre-1.0 development.
 First-time installation:
 
 ```nushell
-git https://github.com/vyadh/nu-test.git
-nupm install nu-test --path
+git https://github.com/vyadh/nutest.git
+nupm install nutest --path
 ```
 
 Usage:
@@ -53,8 +53,8 @@ nutest run-tests
 First-time installation:
 
 ```nushell
-git https://github.com/vyadh/nu-test.git
-cp -r nu-test/nutest <a directory referenced by NU_LIB_DIRS / $env.NU_LIB_DIRS>
+git https://github.com/vyadh/nutest.git
+cp -r nutest/nutest <a directory referenced by NU_LIB_DIRS / $env.NU_LIB_DIRS>
 ```
 
 Usage:
@@ -70,7 +70,7 @@ nutest run-tests
 
 ### Test Suites
 
-A recognised test suite (a Nushell file containing tests) is recognised by nu-test is defined as a filename matching one of the following patterns somewhere within the path:
+A recognised test suite (a Nushell file containing tests) is recognised by nutest is defined as a filename matching one of the following patterns somewhere within the path:
 - `test_*.nu`
 - `test-*.nu`
 - `*_test.nu`
@@ -202,7 +202,7 @@ Typing the following and pressing tab will show all available tests that contain
 run-tests --match-tests parse<tab>
 ```
 
-While test discovery is done concurrently and quick even with many test files, you can specify `--match-suites <pattern>` before `--match-tests` to greatly reduce the amount of work nu-test needs to do to find the tests you want to run.
+While test discovery is done concurrently and quick even with many test files, you can specify `--match-suites <pattern>` before `--match-tests` to greatly reduce the amount of work nutest needs to do to find the tests you want to run.
 
 ### Results Output
 

nutest/report/report_junit.nu

@@ -51,7 +51,7 @@ def testsuites []: table<suite: string, test: string, result: string, output: li
     {
         tag: "testsuites"
         attributes: {
-            name: "nu-test"
+            name: "nutest"
             tests: $"($stats.total)"
             disabled: $"($stats.skipped)"
             failures: $"($stats.failed)"

tests/report/test_report_junit.nu

@@ -158,7 +158,7 @@ def "testsuites with suites" [] {
     let result = $data | testsuites | to xml --self-closed
 
     assert equal $result ('
-        <testsuites name="nu-test" tests="3" disabled="1" failures="1">
+        <testsuites name="nutest" tests="3" disabled="1" failures="1">
             <testsuite name="suite1" tests="1" disabled="0" failures="0">
                 <testcase name="testA" classname="suite1"/>
             </testsuite>

tests/test_integration.nu

@@ -260,7 +260,7 @@ def with-junit-report [] {
 
     test-run-raw $"run-tests --path '($temp)' --report { type: junit, path: '($report_path)' }"
 
-    assert equal ($report_path | open --raw | strip-xml-whitespace) ('<testsuites name="nu-test" tests="6" disabled="2" failures="1">
+    assert equal ($report_path | open --raw | strip-xml-whitespace) ('<testsuites name="nutest" tests="6" disabled="2" failures="1">
   <testsuite name="test_1" tests="2" disabled="0" failures="0">
     <testcase name="test_bar" classname="test_1"/>
     <testcase name="test_foo" classname="test_1"/>