# `cli.test_arguments`

A `jadpo test` command names a path that isn't there, or a seed, a kind or a `--name` it can't use.

Area 14, [Tools](/docs/tooling.md); not declinable; the next step is usually the agent's.

## Why Jadpo refuses it

`jadpo test` runs the tests in a file, a folder or a project, in an order its seed sets. A path that isn't there, or a seed that isn't one, would run nothing, and saying it passed would be wrong.

## What it looks like

The seed isn't a number:


```sh
jadpo test --seed first
```

```text
error: `first` isn't an order seed
  reason: An order seed is a whole number of 0 or more, as a failed test's rerun command shows it.
  next: Give the seed from the rerun command, such as `--seed 48213` (agent)
  rule: cli.test_arguments
  help: https://jadpo.dev/docs/errors/cli.test_arguments
```

`(agent)` at the end of the `next:` line means your coding agent can make the fix itself.

A path that isn't there is refused too:

```sh
jadpo test tests/greet.test.jadpo
```

```text
error: `tests/greet.test.jadpo` doesn't exist
  reason: There is no file or folder at this path.
  next: Give a `.test.jadpo` file, a file and a line as `<file>:<line>`, or a folder (agent)
  rule: cli.test_arguments
  help: https://jadpo.dev/docs/errors/cli.test_arguments
```

## How to fix it

**If you are rerunning a failed test**, use the seed its rerun command gives:

```sh
jadpo test --seed 48213
```

The tests run in the same order as the run that failed.

## Related

- [`jadpo test`](/docs/the-jadpo-command.md#jadpo-test)
- [Running tests](/docs/running-tests.md)