Need to enable the creation and use of template-specific adapter test suites

[geeknoid]

If we want 3rd parties to create adapters for the mixer (goal for Q2), and for our own use, we must create adapter test suites that validate that the common expected functionality for each type of adapter is working as expected.

So for example, we can have a generic quota test suite to ensure that both memQuota and redisQuota adhere to the same semantics.

[jasminejaksic-zz]

Mandar and I decided to move this to Beta milestone, please feel free to change it if you disagree

[geeknoid]

We currently have stated as an objective to have 3 partners write adapters in the Q2 timeframe. Unfortunately, Beta is slated for end of August. It's annoying that we do our internal planning in terms of quarters which don't line up with the release date.

We need to create this suite of test cases before we ask partners to write adapters. That's really the gate I want....

[geeknoid]

Each template type needs a corresponding test suite. Ideally, this could be supplied by the template author.

[ZackButcher]

We have suites for adapter testing for 0.2, but shifting this back to 0.3 to cover the further test suites we want to build.