Re: [appengine-java] Re: non-deterministic datastore behaviour while unit testing

2010-02-04 Thread Ikai L (Google)
We're including helpers for unit testing in 1.3.1. I'm a bit curious as to whether or not this will solve the issues with tests being non-deterministic: https://groups.google.com/group/google-appengine/browse_thread/thread/ddef6d9fa4aa0ae2?pli=1 The fact that it's non-deterministic seems to point

[appengine-java] Re: non-deterministic datastore behaviour while unit testing

2010-02-03 Thread Markus Scheidgen
There are no build errors or missing dependancies. I use the regular buildpath containing only the App Engine SDK Library, JUnit3 Library, JRE System Library plus the external jars: ... eclipse\plugins\com.google.appengine.eclipse.sdkbundle. 1.3.0_1.3.0.v200912141120\appengine-java-sdk-1.3.0\lib\i

Re: [appengine-java] Re: non-deterministic datastore behaviour while unit testing

2010-02-02 Thread John Patterson
On 3 Feb 2010, at 04:22, Markus Scheidgen wrote: But you change it a little bit, maybe comment some unimportant line, and it stops working. hmmm that sounds suspiciously like a build problem. Are you sure the project is always building? i.e. no "missing dependancy" errors in the Eclipse

[appengine-java] Re: non-deterministic datastore behaviour while unit testing

2010-02-02 Thread Markus Scheidgen
No, no caught or uncaught exception what so ever. I tried to create a very simple version of what I was doing. The simplest example, I could imagine, is the following: public class OwnedRelationships extends LocalServiceTestCase { @PersistenceCapable(identityType = IdentityType.APPLICATI