[cdi-dev] split TCK for web-profile and full-profile

[Martin Kouba]

Hi Mark,

in CDI TCK 1.1.x we use TestNG groups [1] to filter out tests that
require either "Web Profile" or "full Java EE platform". So it's really
easy to create a maven profile to run "Web Profile" compatible tests
(just exclude group "javaee-full"). However you're right that the
"sample/canonical" JBoss TCK runner (Weld + WildFly) should contain
three profiles (standalone, incontainer/webprofile, fullplatform). I'm
going to add this one in the next TCK bugfix release (CDI TCK 1.1.1,
Weld 2.0.1).

Martin

[1]
https://github.com/jboss/cdi-tck/blob/1.1/impl/src/main/java/org/jboss/cdi/tck/TestGroups.java


Dne 23.5.2013 08:50, Mark Struberg napsal(a):
> 
> 
> Hi folks!
> 
> This is a common issue in many EE TCKs, but we have the same for CDI.
> 
> The web-profile spec mentions the following:
> 
> "WP.2.3 Additional Requirements 
> Web Profile products must support the deployment of Java EE web
> application modules (.war files). No other modules types are required to be
> supported."
> 
> 
> Thus there is just no necessity to support EAR deployment at all in a web-profile container. 
> 
> 
> We should have 3 categories in our TCK:
> 
> * standalone
> * incontainer (web-profile)
> 
> * infullcontainer (full-profile)
> 
> 
> incontainer might e.g. for EJB get used for the embedded mode.
> 
> 
> 
> txs and LieGrue,
> strub
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>