Taher Alkhateeb <[email protected]> writes:
> I keep forgetting this project carries a lot of history with it. Maybe
> it's because I'm a relatively new. Thank you for sharing Scott, quite
> informative.
Same here.
> If the main advantage is parallelization but that was not really used,
> then maybe it's not super necessary. Maybe one way to think about this
> is instead of making our tests faster, let's make them lighter. For
> example we can switch out from integration tests to unit tests and do
> away with the extra layer of resources being consumed.
An extra argument for prefering unit tests over integration tests is
that they are far more parallelizable since they do to not rely on
shared ressources.
In order to achieve that, more refactoring would be needed to make the
code easily unit testable, such as:
- adding interfaces to decouple implementations
- adding alternate model constructors which doesn't impose passing
an XML element
- removing abuse of inheritance and replace it with delegation
- injecting dependencies instead of embedding them
So Strong +1!
--
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761 070D 0ADE E100 9460 4D37
