The GAE docs talk about how to setup a test to use the datastore. But also follow the instructions here until the docs are fully updated.
Gaelyk - a lightweight Groovy toolkit for Google App Engine Java - 0 views
-
The easiest way to get setup rapidly is to download the template project from the download section. It provides a ready-to-go project with the right configuration files pre-filled and an appropriate directory layout: web.xml preconfigured with the Gaelyk servlets appengine-web.xml with the right settings predefined (static file directive) a sample Groovlet and template the needed JARs (Groovy, Gaelyk and Google App Engine SDK)
-
Running your application locally Google App Engine provides a local servlet container, powered by Jetty, which lets you run your applications locally. If you're using the Gaelyk template, when you're at the root of your project — and we assume you have installed the App Engine SDK on your machine — you can run your application with the following command-line: dev_appserver.sh war
-
Deploying your application in the cloud Once you're at the root of your application, simply run the usual deployment command: appcfg.sh update war
"Manual" UI testing with GWT and App Engine - Google App Engine for Java | Google Groups - 0 views
-
've been able to accomplish what you're doing with Selenium testing. If you're using GWT, then your integration testing and user acceptance probably won't be that far from each other.
-
> My question is this. What's the best way to use LocalServiceTestHelper > so that I can use my app like it has a persistent store? There is no > 'setUp' and 'tearDown' hooks like a JUnit test and the app runs in a > separate process within the IDE. (And in any case, I'm looking to do > integration testing where I want the state to be consistent across a > number of page requests.)
Google Apps account login - Google App Engine | Google Groups - 0 views
-
Yes, you will need to use the federated login (OpenID) stuff. The long-and-short of it is that you pass the federated_identity parameter to users.create_login_url. You'll need to setup a page for users to tell you what goes in federated_identity somehow, perhaps by clicking a google logo or entering an apps domain. For Google accounts: users.create_login_url(federated_identity='google.com/accounts/o8/id') or users.create_login_url(federated_identity='gmail.com') For an Apps account: users.create_login_url(federated_identity='google.com/accounts/o8/site-xrds?hd=yourappsdomain.com') There is a little info here: http://code.google.com/appengine/docs/python/users/overview.html And Wesley has a nice article about it here: http://code.google.com/appengine/articles/openid.html Some info on Google Apps domains and OpenID: http://groups.google.com/group/google-federated-login-api/web/openid-...
1 - 6 of 6
Showing 20▼ items per page