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 test-collection.md #1271

Closed
wants to merge 1 commit into from
Closed

Update test-collection.md #1271

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
4 changes: 2 additions & 2 deletions docs/src/testing/test-collection.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Forge considers all functions in your project marked with `#[test]` attribute as tests.
By default, test functions run without any arguments.
However, adding any arguments to function signature will enable [fuzz testing](./advanced/fuzz-testing.md) for this
However, adding any arguments to the function signature will enable [fuzz testing](./advanced/fuzz-testing.md) for this
test case.

Starknet Forge will collect tests only from these places:
Expand All @@ -21,7 +21,7 @@ Depending on the presence of `tests/lib.cairo` file, the behavior of the test co
If there is a `lib.cairo` file in `tests` folder,
then it is treated as an entrypoint to the `tests` package from which tests are collected.

For example, for a package structured this way:
For example, for a package structured in this way:

```shell
$ tree .
Expand Down