Stripping PHPUnit configuration of elements

[padraic]

Humbug currently, as a first step towards building an XML configuration, strips all filter, listener and logging elements. Assess for potential problems. Do we really need to stripping out code coverage excludes, etc.? Reduce the scope for unexpected problems due to configuration tampering.

[theofidry]

Why do we need to do so? (stripping everything I mean)

[padraic]

At some point there was probably some notion of avoiding conflicts somewhere. Just as there is premature optimisation, there can always be an element of premature bug prevention creeping in. If there are conflicts, better to have them reported than throwing out everything which might be doing who knows what to custom listeners with a genuine purpose.

[theofidry]

Ok, I think we should assume the configuration is legitimate. Maybe we could add an extension point to easily remove some things (I'm thinking of allowing a custom phpunit.xml for example). It otherwise sounds as too much extra work more likely to cause bugs and confusion (due to a greater diff between the PhpUunit config used by Humbug and the one the user expect to use).