Unit testing with simulated eventual consistency by returning correct or stale reads using the set probability distribution.
This allows you to tweak what you're testing - e.g. Just to present everything as consistent stuff for ease of testing, or totally eventual stuff to guarantee that the code you're testing is using keys/transactions etc correctly. They're really the only two scenarios that are interesting for most application unit tests - no one wants intermittent failing tests in the build process. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/6bf9564f-4ca0-4759-b328-5f93c2fac6d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
