How can we cover unit testing for datastore? about google-cloud-python HOT 6 CLOSED

You could use gcd: the local development server, see:
https://developers.google.com/datastore/docs/tools/devserver

from google-cloud-python.

That looks good for local development. It runs on Java right ?

I wonder how difficult it would be to patch in the stubs from AppEngine's dev_appserver.py so that i can use something akin to ext.testbed to unittest locally (ie, without hitting the wire, stay all in Python).

from google-cloud-python.

That looks good for local development. It runs on Java right ?

Yes, it is embedding the App Engine Java development server and running the same servlet that is running in production.

I wonder how difficult it would be to patch in the stubs from AppEngine's dev_appserver.py so that i can use something akin to ext.testbed to unittest locally (ie, without hitting the wire, stay all in Python).

You would have to handle the datastore_v1.proto to datastore_v4 convertion somehow.

Keep in mind that datastore_v4 private interface is not really documented and also subject to change: datastore_v1 is the public versionned interface.

from google-cloud-python.

Yikes. Well I realllly don't want to force people to spin up a local server in order to run unit tests...

We'll have to come up with a way to stub this out.

from google-cloud-python.

#130 adds 100% unit test coverage for modules in gcloud, gcloud.datastore. I would call its strategy "stubbing" (testcases explicitly stub out the http or connection objects) rather than "mocking" (using a general-purpose utilitiy like 'mock').

from google-cloud-python.

#106 exists to cover the deficiencies of testing with stubbed / mocked backends.

from google-cloud-python.