This is the eventually-consistent nature of the HRD. On one hand, there is the argument that your users are going to see this same behavior so you should be coding your tests to accommodate it as well.
On the other hand, maybe this isn't an issue for your users, just your tests. I'm not sure I would do this, but you can turn off the eventual nature of queries on the dev instance, making your tests run as if they're on the master/slave. There are instructions in the documentation. But if you go this route, make sure you *really* understand the consequences. Jeff On Wed, Oct 5, 2011 at 4:19 AM, ezamur <eza...@gmail.com> wrote: > Hi, all > > We are having problems with our integration tests of the app that runs > on GAE. > As you can see from the title, we are using Robot framework, Selenium > server and all of that is nicely integrated with maven and runs on > Jenkins. > > But, the problem is that our tests have a kind of non deterministic > behavior. If I look a single test suite and run it several times (this > stands both for local and app-spot environment) I can get various > results. Tests can pass (which is expected) and they can fail - and > every time they fail, there is no rule which one of them fails. > This specific problem I am referring to emerges when testing storing > objects into GAE. For that we are using Objectify library. > > As I understood from this post > http://groups.google.com/group/objectify-appengine/browse_thread/thread/2395c585161a5274/997c916eecf00f38, > GAE writes are pretty much async operations. So, Objectify gives us > back an ID of newly persisted object which means it is persisted but > when tests redirect us to the page showing the list of the objects, it > can happen that newly persisted object is not in the list. > > My question would what do you do in these kind of situations? I know > why this is happening and that this is not a bug but a feature, but we > cannot accept this kind of behavior during testing. This way we are > never sure if we broke something or everything is just fine, but GAE > decided to be too async in the moment tests were running. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to google-appengine@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
