Currently testing a plugin in isolation is difficult, because you can't reference the framework and plugins don't work on their own.
I'd like to look for peoples input on what the best solution would be.
My ideas are:-
1) Fake the framework. Assuming the plugin only requires ComponentView or QuestionView and Adapt, we can set up the requirejs config to use dummy objects instead. sinon.js will create stub methods that you can use to assert whether they were called correctly too. The down side is that this won't protect from changes to the framework that may break a plugin.
2) Use the actual framework Include the framework as a dependency. Not sure on how to do this gracefully, git submodules are a bit flakey imo, npm package is more maintenance but we can depend on a specific version in the component.