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

Async fixity #615

Merged
merged 2 commits into from Oct 31, 2014
Merged

Async fixity #615

merged 2 commits into from Oct 31, 2014

Conversation

cbeer
Copy link
Contributor

@cbeer cbeer commented Oct 31, 2014

Now taking suggestions for unit testing this... @ajs6f ?
https://www.pivotaltracker.com/story/show/60885728

@ocymum
Copy link

ocymum commented Oct 31, 2014

Maybe you can impl AsyncResponse with a notify() inserted appropriately and synchronize{} on the response during the test?

@cbeer
Copy link
Contributor Author

cbeer commented Oct 31, 2014

Like so?

@ajs6f
Copy link
Contributor

ajs6f commented Oct 31, 2014

Yeah-ish, although I would use a loop around the waiting so that you can distinguish between "timed-out" and "actually failed". Probably just a nicety. fcrepo-jms has an example:

https://github.com/fcrepo4/fcrepo4/blob/master/fcrepo-jms/src/test/java/org/fcrepo/integration/jms/observer/HeadersJMSIT.java

@cbeer
Copy link
Contributor Author

cbeer commented Oct 31, 2014

I'm not sure it's an issue here. If our mock can't respond in under a second, we're in trouble.

@ajs6f
Copy link
Contributor

ajs6f commented Oct 31, 2014

Yeah, I wouldn't freak out about it.

awoods pushed a commit that referenced this pull request Oct 31, 2014
@awoods awoods merged commit ca93748 into master Oct 31, 2014
@awoods awoods deleted the async-fixity branch October 31, 2014 22:31
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

4 participants