> > In fact the "bingo" info is amply documented on the "Local Development > Server Options" documentation page > <https://cloud.google.com/appengine/docs/standard/python/tools/local-devserver-command>, > > where usage for the --require_indexes=yes|no options are described in > detail. >
I was looking for a solution to the problem with testbed in the documentation section that describes automatic testing and could not guess that I need to look for in the description of the development server. The behavior of the 'require_index' parameter in dev_appserver significantly differs from the behavior of the parameter 'require_indexes' in testbed. 1. If the parameter is not specified, the dev_appserver will change the index.yaml file, according reqired indexes. testbed does not change this file, but simply completes all calls to the datastore successfully. 2. To turn parameter on, it's value must be 'yes' in dev_appserver, but 'True' in testbed. 3. If parameter is on, dev_appserver raises errors for missed indexes in index.yaml. testbed raises errors for all requests, that requires indexes, because need parameter 'root_path'. 'root_path' must point to project directory, where index.yaml is placed. So that the parameters of the 'require_index' in the testbed and in the dev_appserver can be considered as different parameters. WBR, Vitaly. -- 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 https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/493416c5-a7f7-4781-9654-68e31cc2ca8c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
