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.

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

What is the reason this project uses inheritance rather than implementing Junit's Rule? #400

Open
BenjaminMalley opened this issue Sep 27, 2023 · 0 comments

Comments

@BenjaminMalley
Copy link

Hi, thanks for this project! I'm curious about the rationale for using inheritance rather than implementing a Junit Rule. If I understand correctly how this works, it seems like the reuse a SparkContext in multiple tests outlined here could be resolved by implementing rule and letting the test implementation decide on granularity using the @ClassRule or @Rule annotations. I'm curious if the Rule approach was tried already and deemed inadequate. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant