The test suite should no longer be a bottleneck

[gonzalo-bulnes]

As a developer
In order to ensure Simple Token Authentication is stable
I want its features to be properly tested

But, while the current test suite performs very well in preventing regressions, it runs (very) slowly, and writing new scenarios is not always trivial. Therefore, testing properly new features uses to take more time than available. One way to work around that time bottleneck is to make the tests suite faster, another is to make contributions easier. Both solutions require in fact pretty much the same preparation.

In order to make the tests suite faster
I want the context of each test to be easier to set, that's to say:
I want unit tests to replace integration tests where possible

In order to make unit testing possible
I want to improve the Simple Token Authentication modules design through refactoring
And I need their interfaces to be properly tested and documented

In order to make contributions easier
And to ensure contributors build on the same interfaces as I do
I want the module both public and private interfaces to be documented
And I want their tests suites to be easy to use and extend

See also: the issues needs testing tag.