9 Mar
2011
9 Mar
'11
9:05 p.m.
On 9 mars 2011, at 20:21, Alexandre Bergel wrote:
Thinking more about this, what I need to do is to reengineer and cut new perimeters inside
the package blueprint blob. More precisely, I would like to define testable perimeters
like:
- querying the model
- building the model beneath the visualization (surfaces + cells)
- describing the visualization with Mondrian
- and describing the browser around with Glamour
That's actually more complicated than I thought originally: there is a strong flavour
of procedural implementation (inherited from the first version in VW), dead code, data
structure which are centralized in the blob and should be put into objects, etc.
So that's what I'm trying to do: read code, what does it do and is it good or bad,
write tests, rewrite if necessary. Since I start from nothing, I don't much test to
guide me but it could be interesting to see these new 'perimeters' evolve through
testing in Hapao.
--
Simon Denier
Right now it
is two steps reverse-engineering, one step reengineering. The code is rather
procedural-oriented with place for improvement with objects. How do you think Hapao could
help?
Hapao help you to quickly increase the coverage of your tests by suggesting which methods
you should focus on.