-
Notifications
You must be signed in to change notification settings - Fork 21
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: add rstest and fixtures #632
base: main
Are you sure you want to change the base?
Conversation
Pull Request Test Coverage Report for Build 13816278472Details
💛 - Coveralls |
test: revert test fix: tests that fixtures werent available fix: add tokyo to tests style: run cargo clippy
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.
fixtures indeed made the code clearer, thanks for this
crates/service/Cargo.toml
Outdated
@@ -74,6 +74,7 @@ tokio-test = "0.4.4" | |||
wiremock.workspace = true | |||
insta = "1.41.1" | |||
test-log.workspace = true | |||
async-std = { version = "1.12.0", features = ["attributes"] } | |||
|
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.
I don't think async-std
is necessary, we're using #[tokio::test]
on every async test case (same thing for tap-agent
)
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.
Looks good to me
Added
rstest
:rstest
this PR aims to make the tests more easy reading and only focusing on the important bits per test
Due to the nature of async fixtures some tests could use them since the test itself needed to be in some order for it to work as intended.