Smoke tests against popular projects

[bartoszmajsak]

As we can now execute Test Bed tests against any repository, we should develop a simple smoke test to see if we can configure our extension against arbitrary projects. The solution could be done as:

• smoke test performing embedded mvn build
  • without extension
  • with extension (and ordering) enabled
  • (up to discussion) as a verification not only build status could be considered, but also amount of executed tests
  • (up to discussion) execution times for both builds could be calculated and if delta is big enough we could fail the test
• maven profile executing only smoke tests
• configurable git repository through system property (executed as part of the build script)

As it turned out in the past, we found several issues already by testing against arquillian-core and spark-java so it's worth a shot.