10 Apr
2009
10 Apr
'09
3:21 a.m.
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?
--
Sergiu Dumitriu
http://purl.org/net/sergiu/