...

1) Developed a maven plugin to trigger the web-based junit tests and analyze the results
2) Configure the pom.xml with cargo plugin to start an embedded Jetty server, deploy the WAR, trigger the web-based junit tests, and stop the server.

Now I have a complete automation.

To avoid repeating the pom configuration for each itest, we can add a profile in the parent pom to support this scheme.

Appendix

Sample results

<?xml version="1.0" encoding="UTF-8" ?>
  <report>
      <testsuites>
          <testsuite name="null" tests="1" failures="0" errors="0" time="0.094">
              <testcase name="testTry(calculator.CalculatorTestCase)" time="0" />
          </testsuite>
      </testsuites>
  </report>

...