Guillaume, this is a great idea. Please file an issue in our issue tracker and we'll follow up.
On Mon, Oct 4, 2010 at 9:50 AM, Guillaume Laforge <[email protected]> wrote: > And I forgot a complementary question: > > Are there plans to add a mocked capabilities service in the testing jar? > > Guillaume > > On Mon, Oct 4, 2010 at 14:08, Guillaume Laforge <[email protected]> wrote: >> Hi all, >> >> I'd like to be able to test how my application is behaving in the case >> of some Capabilities are not enabled. >> For example, what happens when Capability.DATASTORE_WRITE has a status >> of DISABLED. >> I had another look at the testing jar and its various classes, but I >> didn't find a way to see whether we could manually set some capability >> statuses. >> Is this something that is possible? >> What are the best practices in the field? >> >> -- >> Guillaume Laforge >> Groovy Project Manager >> Head of Groovy Development at SpringSource >> http://www.springsource.com/g2one >> > > > > -- > Guillaume Laforge > Groovy Project Manager > Head of Groovy Development at SpringSource > http://www.springsource.com/g2one > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" 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-java?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
