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

Test mode / Insert random errors #2

Closed
robert-bor opened this Issue Mar 23, 2013 · 0 comments

Comments

Projects
None yet
1 participant
@robert-bor
Member

robert-bor commented Mar 23, 2013

The real ObjectStore / network / Internet / you-name-it can have quirks. In order to simulate this quirky behaviour, it would be handy if JOSS could sometimes throw an error on calling a method on the mock ObjectStore.

@ghost ghost assigned robert-bor Mar 23, 2013

robert-bor added a commit that referenced this issue Mar 31, 2013

Issue #2 - the mock implementation now takes a fixed series of http s…
…tatus codes to be returned instead of the mock Swift implementation being called.

@robert-bor robert-bor closed this Mar 31, 2013

katta pushed a commit to twxkit/joss that referenced this issue Oct 6, 2014

Issue #2 - the mock implementation now takes a fixed series of http s…
…tatus codes to be returned instead of the mock Swift implementation being called.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment