-
Notifications
You must be signed in to change notification settings - Fork 19
add tests for basic connector functionality #88
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks pretty good, but I want ask you to split out code and test changes (if it is possible), discuss how tarantool should be started/stopped to test reconnection and note some minor details.
e8cbebc
to
fe03060
Compare
@Totktonada Alexander, please take a look at the code again. I have resolved most of the issues. |
fe03060
to
d2f403a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ztarvos The tests looks good for me. I have the proposal how to run tests locally w/o extra manual steps to get a tarantool instance running. I'll hold the PR to catch your opinion on that.
Added tests for connector API. Closes #51
d2f403a
to
c0f3d12
Compare
Hmm, it stucks second time (I restarted the job) on oraclejdk11 on ClientReconnectIT. It seems it has some race condition. https://travis-ci.org/tarantool/tarantool-java/jobs/457086437#L1455 |
This is the reason why I included code changes in my original PR. |
Got it. So, ok. |
Added tests for connector API.
Fixed involuntary re-connects issue.
Closes #51