-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Refactor sdk tests #21
Conversation
6c12824
to
919cea2
Compare
@@ -0,0 +1,50 @@ | |||
module SdkSupport | |||
class Tracker |
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.
are you venturing into stuff that rspec and mocks would do more easily
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.
Not really. I actually tried using minitest/mock and then mocha, but neither of them were able to do the stuff that I'm doing here as succinctly. It might be a product of poor design since I have the sdk abstracted so far away (stacks effectively call AwsShim.instance.shim.client.method). Not sure if that's a bug or a feature.
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 was thinking about: https://relishapp.com/rspec/rspec-mocks/docs/configuring-responses/returning-a-value#specify-different-return-values-for-multiple-calls, just reminded me of whats happening here.
* refactor tests into simpler stubber procedure * add tests for create and wait * finish testing waiting behavior * move to sdk_support directory * bump version
Also increase test coverage to 100%