The local stubs are at best, stubs. Most of our developers running production environments have setups like this:
- development application locally - new application with data fixtures for integration testing (different app id from main app) - main application - main application with non-default version (staging server against live data) For a beta test, I would advise using the main application because you will be able to roll users' data into the main application when it comes out of beta with no more effort than an updated terms of service and removing the "beta" image. On Wed, Jul 14, 2010 at 1:49 PM, stevep <[email protected]> wrote: > I am at the point where I need to do a full beta test. I'd like to get > a sense from others about the pluses, minuses, and issues related to > setting up a second application for testing vs. continuing to run > everything on my localhost. > > Thanks, > Steve > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- Ikai Lan Developer Programs Engineer, Google App Engine Blog: http://googleappengine.blogspot.com Twitter: http://twitter.com/app_engine Reddit: http://www.reddit.com/r/appengine -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
