[webbeans-dev] The TCK harness
by Pete Muir
If you watch Web Beans SVN, you will have seen a flurry of activity
around the TCK. The TCK harness is now out of development (perhaps
beta quality) and supports:
* reusing the same test cases for incontainer and standalone tests
* declarative definition of test artifacts (a list of classes/xml DDs
for standalone, WAR or EAR for incontainer)
* an html debug mode for incontainer tests
* ability to launch tests and test cases from the IDE, both
incontainer and standalone
* deployment API (currently implemented for JBoss AS)
* porting API which all JSR299 impls must implement to run the TCK
(access to the current manager, ability to activate and deactivate
contexts as needed)
Still to come:
* Ability to execute servlet based requests to test multi-request JSF
and Servlet capabilities (mainly conversation support)
* multiple artifact deployment to support JMS testing and remote EJB
testing
* test launcher for local JVM incontainer tests (EEJB mode)
If you want to read more about developing tests, take a look at http://seamframework.org/WebBeans/JSR299TCKHarness
(still very terse) or if you are interested in using the TCK, take a
look at http://seamframework.org/WebBeans/JSR299TCKPortingPackage -
OpenWebBean's guys, and other JSR299 implementors, I would love your
feedback on using the TCK :-)
Best,
Pete
--
Pete Muir
http://www.seamframework.org
http://in.relation.to/Bloggers/Pete
15 years, 10 months
[webbeans-dev] Formal TCK tests
by Shane Bryzak
For all new tests, could everyone please endeavour to assign the correct
assertion ID (found in tck-audit.xml) to the @SpecAssertion annotation.
This will greatly assist in the accuracy of the TCK coverage report - if
you can't find what you need in tck-audit, please let me know which
assertion your test is for and I'll make sure it is mapped accordingly.
15 years, 10 months
