Or something like cuke4duke.  Not a huge fan of FIT's crippled wiki... but it 
does do the job and you can run tests without having to use the wiki.

-Lennard

----- Original Message -----
From: "Florian Müller" <[email protected]>
To: [email protected]
Sent: Tuesday, March 30, 2010 1:59:40 AM GMT -07:00 U.S. Mountain Time (Arizona)
Subject: RE: opencmis ...ServicesTestProviderFactory needs dependency cleanup

We could move the provider tests and the whole machinery to the FIT module. 
That would also allow us to run the provider tests as integration tests.


- Florian

-----Original Message-----
From: Jens Hübel [mailto:[email protected]] 
Sent: Dienstag, 30. März 2010 08:24
To: [email protected]
Subject: opencmis ...ServicesTestProviderFactory needs dependency cleanup

Hi,

 

I have created a little command line tool around our ObjectGenerator to easily 
feed a repository with test data. The implementation for starting app the whole 
opencmis client engine is very similar to what we do in on our 
XXXTestProviderFactory classes for the SimpleReadOnly and SimpleReadWrite 
tests. Reading the URLs from a system property and initializing the services is 
exactly the same. I would like to reuse the existing factories, but currently 
they are part of the test classes in provider-impl  and do not go into the 
created jars. For the moment I have duplicated the code to opencmis-test-util 
but we should make this useful piece of code reusable. Should we move it to 
test-util and make the tests dependent on this one or is there another good way 
to solve it?

 

Jens

 

Reply via email to