Voting starts in March for the Drupal Association Board election.
yadayada, details follow later.
made me realize that - although the intention and use-case is vastly different - the fundamental code and requirements for introducing default testing configuration are fairly similar to and share a couple of semantics with BDD.
So I hacked together some funny code for default testing config in tests that uses some funny classes and dude even a really fancy (ugly) DI-alike service container that gives you access to default testing config provided by modules, and oh behave, it even works.
A full design, introduction, conversion, and integration of BDD/Behat will take a lot of time, and I definitely do not want to hold off the currently ongoing testing system improvements on that. But it surely can't hurt to explore ways that possibly lead to code that can be more easily migrated in the end.
So let's discuss, Mr. @weitzman, Mr. @beejeebus, Mr. @Sonnabaum! :)
This patch is reduced to the max, so non-functional. Comparing it with the patch above mentioned issue can't hurt to get a better understanding.