jadpo test

Run tests.

Run the project's tests in the interpreter, in an order a seed decides, and report each failure with the values in its assertion, what happened instead and the command that reruns it. Without a path, the project is found by walking up to app.jadpo and every test runs; a file runs its tests, a folder the tests under it, and : the test at that line. The project must check without errors first. With --watch, it keeps running: each save reruns the tests the change reaches, through the compiler's graph, within the path, name and kind given. Every recording of the app's own integrations in shared/providers/ is read by its operation's decoders as a test of its own.

jadpo test [path]

Arguments

• path (optional): A test file, :, or a folder

Flags

• --name <text>: Run tests whose names contain this text
• --kind <kind>: Run one kind, such as pure or recording
• --failed: Rerun the tests that failed last time
• --seed <n>: Run in the order this seed gives
• --watch: Rerun the tests each save reaches
• --keep-failed: Keep a failed test's database to inspect

On every command

• --json: Print data for tools instead of text
• --help: Show every flag, with examples
• --color <when>: Choose when to use colour

jadpo test --json writes one JSON document to standard output instead of text, with the same exit code. The document has schemaVersion, command ("test"), ok, data (what the command produced, null when it failed) and diagnostics (each error with its rule, reason, next and help). A command that needs a terminal refuses --json and names the flags that do the same job.

Examples

# Run every test in the project you are injadpo test# Run the test at line 12 of a file, in the order seed 48213 givesjadpo test domains/planning/libraries/dates.test.jadpo:12 --seed 48213# Rerun the tests that failed last timejadpo test --failed# Rerun the tests each save reaches, until ctrl-cjadpo test --watch# Print the results as data for toolsjadpo test --json

Errors

• cli.test_arguments: Test command has invalid arguments
• test.assertion_failed: Test assertion does not hold
• test.unexpected_failure: Test ended in a failure it did not expect
• test.fault: Test stopped on a fault
• test.subscriber_failed: Subscriber failed for good during a test
• test.failed: Test run failed
• test.no_tests: No tests to run
• test.runtime_start_failed: Test runtime could not start
• toolchain.not_built_yet: Operation is declared but not built yet
• toolchain.project_not_found: Project could not be found