Reduce log level acceptance test permutations

[eatdrinksleepcode]

Currently the acceptance tests take 42 seconds to run on my laptop. More than a third of that time (16.5s) is taken up in the "LogLevels.SpecifyingLogLevel" test, which tests 17 different combinations of arguments, including casing differences and error cases. I think that many of these permutations could be tested at a lower level (component or unit tests), so that the number of permutations that need to be tested at this (expensive) level could be significantly reduced.

[adamralph]

Totally agree. In fact, I think the acceptance tests should generally drop down a level lower to testing the API. This in fact ties in with #214. If we extract the scriptcs specific stuff into a separate assembly then the acceptance tests for that assembly can execute scriptcs, but will be much smaller in scope, and the acceptance tests for Bau itself will all be at the API level and will execute very quickly indeed.

[adamralph]

Marking as on-hold since I think we need to think about #214 first, or at least the refactoring it suggests and the test re-org that may come out of that, in which case this will just be a subset and we can close as a dup.

[eatdrinksleepcode]

Agreed