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

Write tests for S3 store #15

Merged
merged 1 commit into from
Oct 5, 2018
Merged

Write tests for S3 store #15

merged 1 commit into from
Oct 5, 2018

Conversation

hauleth
Copy link
Contributor

@hauleth hauleth commented Oct 4, 2018

This mocks S3 REST API via Bypass. In my humble opinion in this
situation it is better choice than mocking ExAws directly as S3 REST API
is less likely to change and we can test different situations
independently (i.e. network outages) without digging to ExAws internals.

test/imager/store/s3_test.exs Show resolved Hide resolved
test/imager/store/s3_test.exs Show resolved Hide resolved
test/imager/store/s3_test.exs Show resolved Hide resolved
@coveralls
Copy link

coveralls commented Oct 4, 2018

Coverage Status

Coverage increased (+15.8%) to 88.406% when pulling 0014c0d on test-s3-store into 8e111ad on master.

@hauleth hauleth force-pushed the test-s3-store branch 2 times, most recently from 8c9c5c9 to 57b0dea Compare October 4, 2018 23:48
This mocks S3 REST API via Bypass.  In my humble opinion in this
situation it is better choice than mocking ExAws directly as S3 REST API
is less likely to change and we can test different situations
independently (i.e. network outages) without digging to ExAws internals.
@hauleth hauleth merged commit 503f581 into master Oct 5, 2018
@hauleth hauleth deleted the test-s3-store branch October 5, 2018 00:09
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.

None yet

3 participants