[webbeans-dev] TCK status

[Pete Muir]

On 17 Jan 2009, at 20:02, Pete Muir wrote:

> David, Shane and I have now ported all the spec assertion tests to  
> the TCK, giving us about 280 TCK tests and 30 RI unit tests. We have  
> about 20 broken tests and 320 stub tests (many out of dates) in the  
> TCK
>
> Many of the stubs and broken tests are due to not having an embedded  
> EJB  container working or are for web-beans.xml. This is definitely  
> our weakest area - I hope to get this running properly early next  
> week.

Sorry, that sentence got mangled, I meant our coverage of enterprise  
beans is our weakest area.

>
>
> David, could you start working through the broken tests, and see if  
> you can get them working (obviously, if they are EJB ones, leave  
> them for now)?
>
> Shane, could you start working through the stub tests? I would  
> suggest starting with some of the missing lookup ones.
>
>
> On 10 Jan 2009, at 01:13, Pete Muir wrote:
>
>>
>> On 9 Jan 2009, at 22:32, Pete Muir wrote:
>>
>>> We now have started to put the TCK infrastructure in place:
>>>
>>> * TCK porting package APIs to allow the TCK to request the RI do  
>>> stuff like create a SimpleBean from a class
>>> * implementation of these APIs for RI
>>> * Start TCK run and view output (testng format)
>>>
>>> We're now running the TCK (all 5 tests which have been ported so  
>>> far) as part of WB testsuite - currently a single WB RI test is  
>>> responsible for kicking off the TCK run. If the TCK run fails,  
>>> then that test will fail. You won't see a merged testrun total on  
>>> when you run mvn test, however Hudson is correctly reporting the  
>>> merged totals.
>>>
>>> This perhaps isn't the ideal situation, and I'm thinking about how  
>>> to improve it (perhaps run the TCK as another module, rather than  
>>> as part of the RI testsuite, and keep that for RI unit tests).
>>
>> Ok, I found an easy way to resolve this (export the testng.xml file  
>> as a TCK artifact, and then just run it from the RI testsuite). So,  
>> the TCK tests now run as part of the RI testsuite.
>>
>> Shane and I will start an appendix B in the docs, which discusses  
>> how to use the TCK to test a WB implementation.
>>
>> Shane/David, please start removing tests from the RI testsuite as  
>> your port them into the TCK :-)
>>
>>
>>
>>>
>>>
>>> David and Shane have also started work on porting the spec tests  
>>> from the RI unit test suite to the TCK.
>>> _______________________________________________
>>> webbeans-dev mailing list
>>> webbeans-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>>
>> _______________________________________________
>> webbeans-dev mailing list
>> webbeans-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/webbeans-dev
>