-
Notifications
You must be signed in to change notification settings - Fork 439
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
Use parameterization to simplify tests #1552
Comments
Hi, would I be able to take a look at this if that's possible? Don't want to interfere if someone else has already decided to hop on this. |
I don't think anyone else is working on it. Assigned it to you. Thanks for the help! |
Is there a good place that we could put parametrized tests as a starting point or would it be preferred to have this in all applicable areas? |
https://github.com/open-telemetry/opentelemetry-rust/blob/main/opentelemetry-sdk/src/metrics/mod.rs This would be a good place to begin |
Perfect, thank you. I'll get started there |
@sg126 hey just checking if you are still planning to work on this! Let us know if you need help with anything to unblock! |
Hey! Super sorry for the delay, I've been off due to things taking up my time. I will unassign myself. Sorry for the inconvenience! |
@cijothomas can I take up this issue |
Yes sure! Thanks in advance. |
Consider the use of parameterized tests for scenarios where only the inputs and expected outputs differ, to reduce redundant test code. Rust doesn't support it directly, but there are external crates providing this option e.g., - https://crates.io/crates/parameterized_test , or we can create a custom macro as suggested here - https://stackoverflow.com/questions/34662713/how-can-i-create-parameterized-tests-in-rust/
Not related to this PR, for future :)
Originally posted by @lalitb in #1516 (comment)
The text was updated successfully, but these errors were encountered: