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

Make AWS tests SkippableFacts #2080

Closed
sergeybykov opened this issue Aug 19, 2016 · 4 comments
Closed

Make AWS tests SkippableFacts #2080

sergeybykov opened this issue Aug 19, 2016 · 4 comments

Comments

@sergeybykov
Copy link
Contributor

The AWS tests added as part of #2007 and #2008 are failing in the absence of the AWS emulator. Is we turn them to SkippableFacts, we can skip them is the emulator isn't present.

@veikkoeeva
Copy link
Contributor

@sergeybykov They shouldn't be skipped on just any error, but rather on errors failing to connect to the AWS emulator/storage. We could turn this into default functionality too in the future (I would hope without mangling it in class constructors, arguing that's not class but test invariants).

@MikeHardman
Copy link

This will be a consideration for the Kinesis simulator also so I'll need to
follow this pattern here, I'll need the DynamoDB storage emulator that
these tests depend on and an additional emulator for the streaming platform.

On Sat, Aug 20, 2016 at 7:44 AM, Veikko Eeva [email protected]
wrote:

@sergeybykov https://github.com/sergeybykov They shouldn't be skipped
on just any error, but rather on errors failing to connect to the AWS
emulator/storage. We could turn this into default functionality too in the
future (I would hope without mangling it in class constructors, arguing
that's not class but test invariants).


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#2080 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABKeuMlhH4FUu0L-oizHoHWFZVUKwDrvks5qhqI4gaJpZM4Jo8Kr
.

@galvesribeiro
Copy link
Member

@MikeHardman sure, After the last 2 PRs get merged I'll make a cleanup and make the tests (1) isolated on its own projects as suggested by @jdom and (2) make them skippable.

@galvesribeiro
Copy link
Member

I think we can close that after #2095

@jdom jdom closed this as completed Sep 21, 2016
@ghost ghost locked as resolved and limited conversation to collaborators Sep 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants