I'm afraid none of the Cloud API-targeting libraries have testbed support,
as testbed was a solution to App Engine Gen 1-specific problems at the
time. If you have an example of how much slower the datastore emulator is
vs. testbed for your use case, that would be very helpful in prioritizing
further work, either in speeding up the emulator or replicating the testbed
system for Cloud. I'd recommend filing a bug with your experiences at
https://github.com/googleapis/python-ndb/issues (though this would
eventually be tackled by the entire Cloud Client libraries team, rather
than just the NDB team).

On Mon, Feb 24, 2020 at 1:05 PM Remko Tronçon <[email protected]> wrote:

> On Monday, February 24, 2020 at 9:52:25 PM UTC+1, Andrew Gorcester wrote:
> > Cloud NDB is compatible with the Cloud Datastore Emulator; we recommend
> tests be done using that, the same way on Cloud NDB as they would be with
> the Cloud Datastore library.
>
> Using an external emulator is way too slow to use for unit tests, even if
> you are able to get all your code changed so you don’ have to tear down and
> clean start the emulator to avoid interference between tests. This is
> pretty disappointing, and means I (and I expect many others) will be forced
> to rewrite everything if your app isn’t in pure maintenance mode.
>
> Remko
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/google-appengine/9f3246de-d324-4e33-b2d9-86f00a642aa5%40googlegroups.com
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/CANtYgFJY3MAHgOkknEm8WLEFq5-eXQLZwL%3DZ4Dt5G-LU6%3DyicA%40mail.gmail.com.

Reply via email to