LGTM
travis hates it though.

Travis didn't fail on this particular folder, so I'm ignoring it.

Will wait for @waprin to get a chance to review.

@jerjou @waprin I could structure the tests like this:

@py.test.yield_fixture(params=['datastore', 'cloudsql', 'mongodb'])
def app(request):
    ...


@py.test.yield_fixture
def model(monkeypatch, app):
    ...


@flaky(rerun_filter=flaky_filter)
@py.test.mark.usefixtures('app', 'model')
class TestCrudOperations(object):
    def test_list(self, app, model):
        ...

    def test_add(app):
        ...

    def test_edit(app, model):
        ...

    def test_delete(app, model):
        ...

This would require only one use of flaky, and would remove the unused model fixed from test_add while still making sure the fixture is used to clean up any created resources. WDYT?

Either way - as long as there's a comment alluding to the dependency used for cleanup, so future-self won't go on a refactoring spree that messes things up mysteriously :)

These tests are awesome, I would just like to see the pytest magic explained.

These tests are awesome, I would just like to see the pytest magic explained.

I think the class-layout will help with that (usesfixtures helps), but I do want to avoid teaching py.test or talking down to the developer.

Let me switch to that, I think it's all-around easier to grok.

@waprin @jerjou re-organized and added lots of comments and docstrings.

lgtm

Woohoo.