RE: [DUnit-interest] Significant speed improvements to GUI Test Runner

[Martin L. <la...@ru...>]

On Tue, 2005-01-25 at 11:46 -0500, Jud Cole (SOCK Software) wrote:
> I agree totally that in the general case, when looking at a give class
> or
> interface, the property should be generic and that is what is 'called
> flexibility'. In this case, though, I was looking at it from the
> viewpoint
> of the DUnit framework as a whole, and the problem that I see is that
> the
> object is spoken for / used in the GUITestRunner, but not used in the
> TextTestRunner.

Well. The "correct" OO solution would then be to add another class,
a TGUITestCase or whatever. This would then make it rather difficult
to run test both in a text- and a GUI-environment (who said OO was
perfect?).

A better approach would probably be to move the mapping between tests
and=20
nodes to a separate object/list (hash table?) that's only used in the
GUI.=20
But that's much more code to write and test.

A simpler and more pragmatic solution is what's been used here. It works
and
we can add a simple check to make sure the object referenced by the
Object
property is of the correct type, f.x. in a SetObject.

It's also possible to have Object read-only with only a protected or
private
way in. But at this point, we're writing as much convulted code as we'd
write nice code for a hash-table solution... :*)

M.

--=20
Martin Larsson <la...@ru...>