Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update testing.md #89

Merged
merged 1 commit into from
Nov 2, 2024
Merged

Update testing.md #89

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/documentation/testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,10 +73,10 @@ Test can be defined by using the `deftest` macro. This macro is like a function

## Running tests

Tests can be run using the `./vendor/bin/phel test` command. Therefore, the `test` configuration entry must be set (see [Configuration](/documentation/configuration/)).
Tests can be run using the `./vendor/bin/phel test` command. Tests are looked up recursively in all directories set by [setTestDirs](/documentation/configuration/#testdirs) configuration option which defaults to `tests/`.

I can use want to run the test manually on your own, the `run-tests` function can be used. As arguments, it takes a list of namespaces that should be tested.
If you want to run the test manually, the `run-tests` function can be used. As arguments, it takes a map of options (that can be empty) and one or more namespaces that should be tested.

```phel
(run-tests 'my\ns\a 'my\ns\b)
(run-tests {} 'my\ns\a 'my\ns\b)
```
Loading