-
Notifications
You must be signed in to change notification settings - Fork 945
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
Remove or replace ClusterRule #1478
Labels
type: task
A general task
Milestone
Comments
mp911de
added a commit
that referenced
this issue
Nov 2, 2020
Update Javadoc. Add author tags. Remove JUnit leftovers. Exclude JUnit from TestNG depdendency and replace multithreadedtc with series of CountDownLatch. Replace leftover assertNotNull with AssertJ. Upgrade to TestNG 7.3.0 to re-enable RedisPublisherVerification. Original pull request: #1487.
mp911de
added a commit
that referenced
this issue
Nov 2, 2020
Update Javadoc. Add author tags. Remove JUnit leftovers. Exclude JUnit from TestNG depdendency and replace multithreadedtc with series of CountDownLatch. Replace leftover assertNotNull with AssertJ. Upgrade to TestNG 7.3.0 to re-enable RedisPublisherVerification. Original pull request: #1487.
sokomishalov
added a commit
to sokomishalov/lettuce
that referenced
this issue
Nov 4, 2020
Original pull request: redis#1487.
sokomishalov
pushed a commit
to sokomishalov/lettuce
that referenced
this issue
Nov 4, 2020
Update Javadoc. Add author tags. Remove JUnit leftovers. Exclude JUnit from TestNG depdendency and replace multithreadedtc with series of CountDownLatch. Replace leftover assertNotNull with AssertJ. Upgrade to TestNG 7.3.0 to re-enable RedisPublisherVerification. Original pull request: redis#1487.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To entirely remove JUnit 4, we need to rework tests using
ClusterRule
. Ideally, we extract code from the rule into some utilities since the rule mainly issues a flushall on all nodes (Lettuce can do that already through the standard connection interface).The text was updated successfully, but these errors were encountered: