-
Notifications
You must be signed in to change notification settings - Fork 92
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
Riak 2 Feature: Security #149
Conversation
|
||
describe 'without authentication configured' do | ||
let(:options){ Hash.new } | ||
it 'should start a tcp connection and not start a tls connection' do |
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.
I worry that these tests basically describe an implementation (too many doubles). Is there a way to exercise the class at a higher level, or more like blackbox? Integration tests are fine.
Another option might be like the "mock server" we had previously where it would actually create a server-side version and you could verify what came across the wire.
You can also tell me to buzz off. 😁
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.
Yeah, there's already an integration test that hits these parts. The problem with those is that they require many different Riak configurations, and right now that means they basically don't get run on a regular basis. I'd prefer to keep these as a safety net, and I'm not sure if there's a much better way to express these.
|
This works as advertised when using this PR to riak-ruby-vagrant: basho-labs/riak-ruby-vagrant#4 👍 |
Conflicts: lib/riak/locale/en.yml
The Ruby client needs to support security per basho/riak#355 .
(copied from #110 )