There are two ways to run Q7 tests in continuous integration environment:
- Via Q7 Runner in a command line, suitable for builds based on ANT/shell scripts.
- Via Q7 Maven Plugin, suitable for Tycho builds.
Q7 Maven Plugin automatically invokes Q7 Runner with a command line arguments based on POM configuration, therefore all information below is equally applied both to Q7 Maven Plugin and Q7 Runner.
As an execution result, Q7 Runner produces JUnit XMaL report, which is understood by Continuous Integration servers such as Jenkins/Hudson and Atlassian Bamboo, and human-readable HTML report.
One of the great advantages of Q7 Runner is that you don't need to build a complete RCP in order to run Q7 tests – it can create application-under-test using update site(s) and existing RCP, such as Eclipse SDK or Eclipse Platform, more on this is is described in our blog – http://www.xored.com/2013/04/23/test-your-plugins-on-multiple-versions-of-eclipse/.
Starting from version 1.3, Q7 uses pricing and licensing model based on execution count. According to this model, it does not matter how many Q7 runners and IDEs are used and pricing depends on a total test execution count per month associated with a person/company. More information is available at http://q7.xored.com/pricing. Therefore, in order to execute tests using Q7 Runner/Q7 Maven Plugin it is required to specify credentials in command line arguments or POM configuration. Instead of username and login, Q7 Runner uses as credentials the following parameters: