Indeed, automated testing should be mandatory in a quickstart.
On 24 Feb 2014, at 16:03, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
all quickstarts should have common / same testing pattern!
End result must be that we can do mvn clean test/integration-test -P<some profile>
and it would test the quickstart.
If we would run this in root folder it would test all quickstarts against target
When we have this, we can test quickstarts on CI and have another set of tests to make
sure we didn't break anything in nightly WildFly builds.
On Mon, Feb 24, 2014 at 4:14 PM, Eduardo Martins <emartins(a)redhat.com> wrote:
There is now a fully working set of WildFly Quickstarts at
, and a set of dev friendly Maven BOMs at
So what’s next? Here are some ideas:
* integration at wildfly.org
* upgrade existent quickstarts to take advantage of Java EE 7 new features, for
instance the default managed objects such as java:comp/DefaultDataSource
* add new quickstarts wrt the new Java EE 7 technologies (Batch, EE Concurrency
wildfly-dev mailing list