Note that there are some explanatory texts on larger screens.

plurals
  1. POGWTTestCase with Database not working
    primarykey
    data
    text
    <p>how do i create integration tests that use the services (requestfactory) and also the JDO-persistancemanager to save and retrieve data.</p> <p>the GWTTestCase + requestfactory is working just fine. normal JUnitTests also work with the database but are testing just the serverside (with LocalServiceTestHelper)</p> <p>i tried using the LocalServiceTestHelper also in the GWTTestCase but the compiler can't import the code:</p> <pre><code> [ERROR] Line 3: The import com.google.appengine.tools.development cannot be resolved [ERROR] Line 15: LocalServiceTestHelper cannot be resolved to a type </code></pre> <p>however, the libs appengine-api-labs.jar appengine-api-stubs.jar appengine-api.jar appengine-testing.jar are in the classpath! if i am not using the LocalServiceTestHelper i am getting the "java.lang.NullPointerException: No API environment is registered for this thread".</p> <pre><code>java.lang.NullPointerException: No API environment is registered for this thread. com.google.appengine.api.datastore.DatastoreApiHelper.getCurrentAppId(DatastoreApiHelper.java:80) com.google.appengine.api.datastore.DatastoreApiHelper.getCurrentAppIdNamespace(DatastoreApiHelper.java:90) com.google.appengine.api.datastore.Key.&lt;init&gt;(Key.java:97) com.google.appengine.api.datastore.Key.&lt;init&gt;(Key.java:87) com.google.appengine.api.datastore.KeyFactory.createKey(KeyFactory.java:84) </code></pre> <p>i was looking for a solution about 3 heuers but i can't find anything</p> <p>thanks for your help!</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload