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

unit tests are not written to always succeed in GAE dev environment #746

Closed
mitchellsundt opened this issue Jul 9, 2015 · 0 comments
Closed

Comments

@mitchellsundt
Copy link
Contributor

mitchellsundt commented Jul 9, 2015

Migrated to getodk/aggregate#38 by spacetelescope/github-issues-import

Originally reported on Google Code with ID 745

Many of the unit tests of the persistence layer assume if you put() a value, then an
immediate get() will retrieve it. This is not true in the parallel datastore dev environment.


And production code shouldn't be doing immediate fetches anyways.

Need to look into how to correctly flush GAE datastore during unit tests so these random
errors don't occur.

Reported by mitchellsundt on 2013-01-17 02:52:09

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants