[MRUNIT-140] TestDriver should use composition and have less responsilibities

• Type: Task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.0.0
• Assignee: Bertrand Dechoux
• Reporter: Bertrand Dechoux
• Created: 13/Aug/12 07:26
• Updated: 12/Nov/12 10:06
• Resolved: 12/Nov/12 10:02

Description

Due to more and more (welcomed) refactorings, TestDriver is becoming bigger and bigger. Reducing code duplication is a good thing. But TestDriver begins to have too many responsibilities. A solution would be to use composition in order to extract responsibilities from it.

I currently see a few topics that could profit from it:

• Errors recording
• Distributed Cache
• Counter validation

You are welcome to suggest more. This work might in the end also help with the implementation of the new API by providing a cleaner internal organisation of MRUnit.