Currently, IMObjectEditor implementations are excluded from unit testing as they are too difficult to test via traditional means.
A test harness is required in order to test them via their rendered echo2 components.
Given an IMObjectEditor instance, it should be possible to access its Component and child Components via a special naming scheme.
The naming scheme will be based on the nodes in the IMObject being edited.
E.g, given an IMObjectEditor for a party.customerperson:
IMObjectEditor editor = // create party.customerperson editor
Component root = editor.getComponent();
setProperty(root, "firstName", "Joe");
setProperty(root, "lastName", "Bloggs");
select(root, "contacts"); // select the "contacts" tab
select(root, "contacts.archetypes", "contact.location"); // select the location contact in archetype dropdown
select(root, "contacts.add"); // press the add button to add a new contact
setProperty(root, "contacts", "address", "333 Some Road" );