-
Notifications
You must be signed in to change notification settings - Fork 8
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.
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
test: separate out tests #103
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should agree on a standard way to name tests. I think the most straightforward is to have the test source with same name as the logic source the tests refer to, rather than introducing new names (e.g. basic
).
According to the above, it would also be great if there is no lib.rs under tests, in the sense that the tests that are currently present there (e.g. rln, semaphore) should be moved to/merged with tests with creates where such functionalities are implemented (e.g. semaphore/lib tests should be moved under tests/protocol.rs, etc.)
Also I see tests in rln/public were not moved and also some other ones.
708730e
to
70390ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great PR! LGTM!
The only test I see should still be moved is https://github.com/vacp2p/zerokit/blob/test/separate-tests/semaphore/src/protocol.rs#L217, please do it before merging.
Whoops, missed that. Will refactor |
Move tests to standalone
tests
directory in each submodule