-
-
Notifications
You must be signed in to change notification settings - Fork 358
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
Update to Scalatest 3.1.x #320
Conversation
@holdenk Hello, I am mentioning you here to hopefully draw your attention. Is there any interest in merging this PR ? This would be helpful to bump scalatest in different projects (as this is a blocker). All the best |
@nightscape - Your PR looks good, but it might be best to remove the Scalatest dependency from spark-testing-base altogether. As you know, Scalatest isn't just a test dependency, it's a project dependency. Removing the Scalatest dependency would allow spark-testing-base to be used with other testing frameworks like munit and utest. It'll also prevent the cross compilation matrix from getting too complicated... not sure we want to cross compile with Scala version / Spark version / Scalatest version. Removing the Scalatest dependency should be relatively easy and could be done in a backwards compatible manner. Let me know your thoughts! |
Hey @MrPowers, good idea! |
@holdenk - hope you're recovering well. Really sorry to hear about the motorbike accident. @nightscape - Would this PR make spark-testing-base unusable for Scalatest 2.x users? I am assuming that It's unfortunate Scalatest made these breaking changes. It's really hard to maintain a Spark library with all these Scalatest / Spark / Scala version moving parts. Big shout out to @holdenk for maintaining this lib for all these years! |
@holdenk thanks for your hard work and I hope you are getting better. To what I understand, you are not really in favor of the merge of this PR as is due to compatibilities breaks ? I am not sure if this is a bad idea to merge this PR as is. Since it would encourage people to bump their scalatest versions due to compatibility. How would you remove the scalatest dependency @MrPowers ? As a side note : 3.1.X is compatible with 2.X, 3.0.X and 3.2.X. This might be worth to merge this, release and open a ticket to remove scalatest dependency ? WDYT ? |
Here's a code snippet that is extending from a scalatest trait. trait DataFrameSuiteBase extends TestSuite
with SharedSparkContext with DataFrameSuiteBaseLike { self: Suite => The main reason to extend We'd have to reimplement methods like
|
c0646b6
to
92d461e
Compare
I just rebased this commit. |
@holdenk Could you please merge this PR ? We are not able to use spark-testing base for 3.2.1 upgrade. I saw your release version 1.1.2 but it is still failing with 3.2.1 |
#354 - We have created the issue here. |
Looks good, I'll probably have to do a larger version bump for the dep change. |
@holdenk thanks for merging this. Could you please help in releasing the jar ? |
Should be available as 1.2.0 |
Thanks @holdenk . https://github.com/holdenk/spark-testing-base/releases - Release is not updated here. It is available in mvn repo. |
The update is a 2-step process where you first update to 3.0.8 and use Scalafix to fix deprecations.
Then you repeat the same process with 3.1.x.
I've made 2 commits out of those but you can also squash them into one if you don't care about the intermediate step.