Re: [mylyn-integrators] integration test

[Steffen Pingel <steffen.pingel@xxxxxxxxxxx>]

Many of the JIRA tests work that way: One or more tasks are created through the JIRA API and then a high-level Mylyn API call is invoked and the result is verified. Take a look at JiraRepositoryConnectorTest or JiraTaskDataHandlerTest for examples. 

The Trac tests work in a similar way except that most tests expect certain tasks to be present in the repository. This is mostly due to historical reasons when the Trac API did not support task creation. I would generally recommend to do all setup in your tests as this makes testing new repository versions or other instances than your particular test repository very easy.

Steffen

On Mon, Mar 30, 2009 at 4:56 PM, Larry Edelstein <ledelstein@xxxxxxxxxxxxxx> wrote:

Has anyone written an integration test that verifies how their connector synchs with their database?

 

I'd like to write a test that creates a new task repository with my connector, then synchs with the database, then verifies that the local repository data is correct, and the remote database data is correct.

 

It seems like I need to know how to do all of these programmatically:

 

- create and configure a task repository

- trigger a sync

- await sync completion

- examine task repository data

 

Does anyone have any examples, or ideas?

 

Larry Edelstein

Senior Member of Technical Staff

salesforce.com

ledelstein@xxxxxxxxxxxxxx

(415) 713-9148

_______________________________________________
mylyn-integrators mailing list
mylyn-integrators@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mylyn-integrators

-- 
Steffen Pingel
Committer, http://eclipse.org/mylyn
Senior Developer, http://tasktop.com