The development datastore generates all of the needed indexes, so as long as you're exercising every possible query there shouldn't be any missing indexes.
If you insist on testing for missing indexes, you can set setNoIndexAutoGen<https://developers.google.com/appengine/docs/java/tools/localunittesting/javadoc/com/google/appengine/tools/development/testing/LocalDatastoreServiceTestConfig.html#setNoIndexAutoGen(boolean)>to turn off index generation and then attempt to call a query. If the query fails to complete, then the usual culprit is that the index is missing. You can confirm that by looking at the logs, or you can automate it by using the Logs API. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com On Thu, Apr 17, 2014 at 5:49 AM, sarath upadrista < [email protected]> wrote: > Any suggestions for this. > > Basically I would like to know what are the required indexes while > running JUnit tests? > > > On Tue, Apr 15, 2014 at 3:56 PM, sarath upadrista < > [email protected]> wrote: > >> Hello, >> I would like to know how the JUnit test uses the datastore-indexes >> while doing the queries. >> >> My problem is that, I would like to track the missing >> datastore-indexes using the JUnit test. Is there any way to give the >> indexes file as an input while configuring the datastore? >> >> I don't want to use the auto datastore-indexes for my JUnit tests. >> >> What configuration can I make so that JUnit will be able to suggest what >> are the missing indexes? >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
