Awesome, thanks!

Florent

On Wed, Oct 27, 2010 at 10:24 PM, Florian Müller
<florian.muel...@alfresco.com> wrote:
> Hi Florent,
>
> All tests and all test groups are now automatically also JUnit tests.
> Make sure that you to set the system property 
> "org.apache.chemistry.opencmis.tck.junit.parameters" to the filename of the 
> OpenCMIS session parameters file. Otherwise it doesn't know to which 
> repository it should connect to.
>
>
> Cheers,
>
> Florian
>
>
> On 27/10/2010 18:21, Florent Guillaume wrote:
>> Thanks Florian.
>>
>> To debug things I really like to run individual tests or groups of
>> tests from my IDE.
>>
>> I understand from your previous email that there are reasons to not
>> use JUnit directly for the TCK's tests, but couldn't some way be
>> devised to allow them to reuse parts of JUnit for the runners and
>> grouping and individual testing, so that we can still leverage IDE's
>> integration with the standard test frameworks?
>>
>> Anyway, no urgency, but I wanted to share my thoughts.
>>
>> Florent
>>
>>
>> On Wed, Oct 27, 2010 at 5:51 PM, Florian Müller
>> <florian.muel...@alfresco.com>  wrote:
>>> Hi all,
>>>
>>> I have checked in the TCK framework. There are currently only a handful of 
>>> tests but it will grow over time.
>>>
>>> Here are few instructions how to use it and how to add more tests:
>>>
>>> - The easiest way to run the TCK is 
>>> org.apache.chemistry.opencmis.tck.runner.ConsoleRunner .
>>>   This little program starts the TCK and prints a text report on the screen.
>>>   It requires one command line parameter: the path and filename of a file 
>>> that contains OpenCMIS session parameters.
>>>   A sample file is in the resource folder.
>>>
>>> - If you are more adventurous you can try the ant task. This also allows 
>>> you to change the output format.
>>>   There is a build.xml sample in the resource folder.
>>>
>>> - At the moment, there is only one test group and three tests. They are all 
>>> in org.apache.chemistry.opencmis.tck.tests.basics .
>>>   Have a look and let me know if this is understandable.
>>>
>>> - If you want to create a new test extend AbstractSessionTest and implement 
>>> init() and run(). Don't forget to set a test name!
>>>   Finally, add your test to the init() method of your test group.
>>>
>>> - If you want to create a new test group extend AbstractSessionTestGroup 
>>> and implement init(). Don't forget to set a group name!
>>>   If the group should be included in the default TCK groups, add a new line 
>>> to cmis-tck-groups.txt .
>>>
>>>
>>> It might look a bit complex and verbose at first sight. But keep in mind 
>>> that these are not unit tests.
>>> If we want to generate a decent report, we have to do a bit more than just 
>>> simple asserts.
>>>
>>> Comments?
>>>
>>>
>>> - Florian
>>>
>>
>>
>>
>
>



-- 
Florent Guillaume, Director of R&D, Nuxeo
Open Source, Java EE based, Enterprise Content Management (ECM)
http://www.nuxeo.com   http://www.nuxeo.org   +33 1 40 33 79 87

Reply via email to