test

Run tests for a specific feature or pattern and summarize the results.

Arguments

• $ARGUMENTS — feature name or test name pattern (optional). If omitted, runs all tests.

Steps

1. Determine the test command:

   • If $ARGUMENTS is empty, run all tests:

     npm test
     

   • If $ARGUMENTS looks like a file path (contains / or .js), run that file directly:

     node --test $ARGUMENTS
     

   • Otherwise treat it as a name pattern and run:

     node --test --test-name-pattern "$ARGUMENTS"
     

2. Capture the full output.

3. Parse the results and produce a summary:

TEST RESULTS — <feature or "all tests">
=========================================

✅ Passed:  12
❌ Failed:   2
⏭️  Skipped:  1
Duration:  0.43s

FAILURES:
  ✗ POST /users — should return 400 for missing email
    at test/features/users/users.router.test.js:58
    AssertionError: expected 400, got 200

  ✗ GET /users/:id — should return 404 for unknown id
    at test/features/users/users.router.test.js:91
    AssertionError: expected 404, got 500

1. If all tests pass:

✅ All X tests passed.

1. If there are failures, point to the exact file and line number for each, and briefly describe what assertion failed to help the user navigate directly to the issue.

Rules

• Never modify test files or source files.
• If the test command exits with an error before running any tests (e.g. syntax error, missing file), report the raw error clearly.
• Do not retry failing tests automatically.