Hi folks,
I would like to give some information about our current TCK status and how OWB
works against RI TCK
There are 3 types of TCK testing
1* Standalone tests
*These are tests that are not needed to use fully compliant Java EE 6.0
server. These are simple unit tests.
* Does not need any Java EE or EJB container functionality.
* OWB pass 389 of 580 standalone tests!
* You can also run those tests via
-> mvn test in webbeans-tck
2* Integration tests
* These are tests that are run inside fully compliant Java EE 6.0 server.
* As an experience, some tests are unique to Weld (RI implementation)
https://jira.jboss.org/jira/browse/CDITCK-59
* After we integrate with Geronimo, we re-try to pass those integration
tests.
3* Embedded EJB or Java EE web profile container tests
* These are tests that are run inside embedded EJB container or Java EE web
profile
* Currently this type of TCK is not developed by the Weld Team. It is an
issue.
https://jira.jboss.org/jira/browse/CDITCK-85
https://jira.jboss.org/jira/browse/CDITCK-51
https://jira.jboss.org/jira/browse/CDITCK-52
* I have been trying to run those types of the inside OpenEJB+Tomcat
container.
- To run integration tests, update jboss-test-harness.properties in the
webbeans-tck as follows
org.jboss.testharness.standalone=false
org.jboss.testharness.runIntegrationTests=true
- We have to update some configuration of TCK to run tests. I send an
email about issue, but there is no response!
* All of the standalone tests are also run in OpenEJB+Tomcat
http://lists.jboss.org/pipermail/weld-dev/2009-December/002058.html
Thanks;
--Gurkan
___________________________________________________________________
Yahoo! Türkiye açıldı! http://yahoo.com.tr
İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyor!
