archetype-itests

Archetypes Integration Test

This module generates every archetype in the generated archetype-catalog as a project in target/createdProjects and then creates an uber pom in target/createdProjects/pom.xml and then checks that all the projects build and pass their system tests via Fabric8 Arquillian .

Testing all the archetypes build OK

Run the following

mvn clean test

Running Arquillian tests for each project

To enable the arquillian tests on each project type the following:

mvn clean test -Dtest.arq=true

NOTE: make sure that your current shell can connect to both docker and a kubernetes or openshift cluster before trying to run this! If you use minikube or minishift you will need to run one of these lines in your current shell:

eval $(minikube docker-env)

eval $(minishift docker-env)

NOTE that OpenShift is currently only supported in kubernetes mode for now until we get Arquillian working with S2I binary builds and ImageStreams! When running on OpenShift we currently default to kubernetes mode.

If you want to try things on OpenShift in openshift mode (using S2I binary builds and ImageStreams) then run the tests as follows:

mvn clean test -Dtest.arq=true -Dfabric8.mode=openshift

Viewing the output

Running all the tests can generate quite a bit of output :)

To browse or grep the test output see: target/test.log

Testing a single archetype

Once you have built the generated projects you can just cd into the generated project folder and run things there directly

cd target/createdProjects/spring-boot-camel-archetype-output
mvn clean install  -Dfabric8.mode=openshift -Dfabric8.build.recreate=all
mvn failsafe:integration-test failsafe:verify

Or to just generate a signle single archetype you can specify a system property test.archetype in this folder when you run a build:

mvn clean test -Dtest.archetype=cdi-camel-archetype

Keeping track of failing archetypes

When an archetype fails its system test we should remove it from the catalog by excluding it from the archetypes/pom.xml file and create an issue for it.

You can view all the current failing system test issues