searls/jasmine-maven-plugin — pull request #139 by kreyssel (2013-02-11 13:13:16+00:00)
Title: Switch to use provided "examples" as full tested it cases

I do not know how well tested the provided tests under src/test/resources/examples. But I made a little change to use this "examples" for full tested IT cases and all tests run gracefully. :-) The pull request moved all sources within src/test/resources/examples to src/it (because of maven-invoker-plugins default source folder).

This IT cases are automatically launched after mavens packages phase
via maven-invoker-plugin (see
http://maven.apache.org/plugins/maven-invoker-plugin/usage.html) if you do build like "mvn clean install".

The maven-invoker-plugin clones every single project (folder) from src/it/* to
target/it and use a local maven repo under target/local-repo. Then runs
the IT case as "mvn clean install" (or the given settings from
invoker.properties file located in project folder) and validates the
expected build state. If a "special" build state is expected, a
"postBuildHookScript" exists (verify.groovy) in the project folder to
validate the build result and the build messages.

Hint 1: The "backwards-compatible" tests use a new parent pom.
Eventually all "backwards-compatible" tests should moved directly to src/it.

Hint 2: The test "jasmine-webapp-advanced-requirejs" fails on my
cloudbees jenkins instance, because it tries to download files from
remote locations (http://requirejs.org/) thats not supported. I do not know how TravisCI does.

Hope this helps. :-)