On Fri, Apr 10, 2009 at 8:10 AM, Asiri Rathnayake < [email protected]> wrote:
On Fri, Apr 10, 2009 at 6:51 AM, Sergiu Dumitriu <[email protected]> wrote:
Hi devs,
All the components that depend on the model bridge need to provide a mock implementation of the bridge, which has as a main disadvantage the fact that the code is hard to updade (if I change the bridge, why would I look inside the office importer?)
We currently have 4 mock implementations.
A better approach: Make one mock implementation inside the bridge component, which will be packaged in a test package, and which will be used as a test-time dependency when needed.
WDYT?
+1
Ummm, on second thoughts, different components might require their MockDocumentAccessBridges to behave differently... How do we handle this situation? - Asiri