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

Increase currying test coverage (#2894) #2939

Merged

Conversation

lgtout
Copy link
Collaborator

@lgtout lgtout commented Feb 21, 2023

This PR achieves 100% test coverage for curried, uncurried, curriedEffect, and uncurriedEffect.

Arity-22 uncurriedEffect was missing, so I added it and updated arrow-core.api.

Currently Kotest's checkAll, forAll, forNone do not support tests with more than 12 generators.

As such, I had to submit a PR to Kotest to support up to 22 generators in order to use property testing on Arrow's curry functions.

The Kotest PR has been merged into master and is due to ship in the next release (5.6.0). But it's unclear when that will be.

I was able to use the Kotest update by adding the snapshot repository address
https://s01.oss.sonatype.org/content/repositories/snapshots/ and setting Kotest version to 5.6.0.1188-SNAPSHOT. But I didn't include those build changes in this PR.

As such, this PR will fail the Arrow pipeline. Other than that, the PR is complete.

Related: closed draft PR to get feedback on general direction of changes.

@serras
Copy link
Member

serras commented Mar 24, 2023

@lgtout would it be possible to comment out the code which doesn't work because of the required Kotest changes, so we can merge the one that works and then put the commented out one back when Kotest is updated?

@lgtout
Copy link
Collaborator Author

lgtout commented Mar 24, 2023

@serras Yes, I can modify this branch to have just the tests that don't require the Kotest update.

@serras
Copy link
Member

serras commented Mar 31, 2023

@lgtout I've move forward and commented out the tests myself. Is there something else you want in this PR, or could be mark it as ready for review?

@lgtout
Copy link
Collaborator Author

lgtout commented Mar 31, 2023

Thank you @serras . No, nothing else. Can be marked as ready-for-review.

@serras serras marked this pull request as ready for review March 31, 2023 13:01
@serras serras requested a review from a team March 31, 2023 13:01
@nomisRev nomisRev merged commit 493a22d into arrow-kt:main Apr 3, 2023
@nomisRev
Copy link
Member

nomisRev commented Apr 3, 2023

Thank you @lgtout! 🙌

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

Successfully merging this pull request may close these issues.

3 participants