Continuous Integration (Jenkins) With intaQt ¶
The following tutorials will show you how to use the Jenkins continuous integration (CI) system to run intaQt test cases within a CI environment.
This tutorial assumes that you know how to use intaQt Client. If you have not used intaQt Client before, please see our intaQt Client tutorial. This tutorial also assumes that you are familiar with the basics of version control (for example, Git or Subversion).
|Admin access to Jenkins Server is necessary to follow the steps in the tutorials.|
1. Required QiTASC Products¶
The following products must be installed and running using the QiTASC Cockpit in order to run intaQt test cases via Jenkins:
intaQt - This should be running on a remote machine.
ADM with Android SDK - This should be on the same machine on which intaQt is running.
intaQt Client - This must be the same version as for intaQt.
For detailed installation instructions, please refer to the intaQt manual's intaQt Installation section.
2. Infrastructure and Prerequisites¶
In addition to the above QiTASC products, the following must be set up and running:
All Jenkins Build Agents must have intaQt Client installed: Test cases will be executed via intaQt Client.
A Jenkins CI environment (a Jenkins Server and optional Jenkins build agents).
- If using a Jenkins Agent, intaQt Client must also be installed on the Agent.
An intaQt project that is under version control.
- If you do not have a project available, create the basic project that is described in the intaQt Client tutorial.
|There is always a Jenkins Server and there are always Jenkins Build Agents, however but a Jenkins Server can also be used as a Build Agent.|