CODEWITHSUNDEEP
unit-testinggoogle-app-enginerestgoogle-cloud-datastore
Matt Norris
Matt Norris

Reputation: 8836

How do I unit test REST methods in App Engine?

I haven't found a way to test REST methods for my application automatically, while using setUp and tearDown methods to preserve the uniqueness of each test.

gaetestbed gives me a clean datastore in between tests. And httplib2 allows me to easily call REST methods and parse their responses; but in order to do so, a local instance of my application must be running on port 8080 and called each test. This defeats the purpose of a gaetestbed-like refresh of the datastore, since data is preserved in between calls.

I could start and stop the GAE server within the setUp and tearDown methods, but this seems wasteful and time-consuming. Is there a better way?

Upvotes: 0

Views: 346

Answers (2)

Nick Johnson
Nick Johnson

Reputation: 101149

Using gaetestbed, or your own unittest code like this, simply instantiate your handler classes directly, using a mocked/fake environment dictionary, and call the methods (initialize() and get()/post()/etc in the case of webapp) directly.

Upvotes: 3

Ben
Ben

Reputation: 1030

When doing functional tests using REST methods we ended up writing helper calls to clean out the internal caches and force our engine to sync with the database.

I haven't used gaetestbed, but I would have thought that you could flush the datastore between tests? 

"Use case: develop and test locally with real data
Restore to: your local development server.
Once you have restored the data to your local development server, I would highly suggest that you take a backup of your datastore.
You can find your datastore files in a temporary folder on your local machine (e.g., on my Mac, it's /var/folders/bz/bzDU030xHXK-jKYLMXnTzk+++TI/-Tmp-/). To find the folder on your own machine, flush the datastore (./manage.py flush) and you will see the path to your datastore folder printed in the resulting output."

Upvotes: 0

Related Questions