| [mylyn-integrators] integration test; importance of ITask attributes? |
|
I have an integration test that - creates some tasks in my native task database - calls connector.getTaskData(..) - calls TasksUi.getRepositoryModel().createTask(..) - calls connector.updateTaskFromTaskData(..) - verifies that the task has the right summary, owner, etc. Question: instead of making those three calls, is there a
less granular call I can make to get the same result? I'm also wondering if I should bother mapping attributes
into the task when they're not represented by any methods in ITask. For
instance, comments aren't covered by ITask. In my integration test, I
want to verify them, but unless I explicitly set them, perhaps by overriding
applyTo(ITask) my own subclass of TaskMapper, I have to find them in the
taskData, rather than the task. I gather that ITasks are lightweight facades for heavier
TaskData, so maybe I shouldn't. Thoughts? Larry Edelstein Senior Member of Technical Staff salesforce.com ledelstein@xxxxxxxxxxxxxx |