Qualitia supports Team City, a Java-based build management and continuous integration server. Integrating Team City helps you improve quality of software release with minimal efforts. Reports integrated with CI tools make it easy to analyze defects or failures with detailed information logs. These reports are available on demand and by emails upon completion of test executions.

You can integrate Qualitia to execute test cases through TeamCity. In order to do so, you must configure your offline package accordingly.

Team City Installation

In order to use TeamCity as the CI tool, you need to download and install some software packages that help you in executing test cases using Team City.

Download TeamCity and JRE 6, 7/JDK 1.6, 1.7.
Install downloaded JRE /JDK.
Right-click TeamCity setup.exe and select Run as Administrator.
Follow the instructions that appear on the screen.
Post Team City installation, install Team City agent.
Open the Run window, go to services.msc, and stop Team City agent service.
Open the Command Prompt window as administrator and browse to the agent.bat file.
Once the setup is complete, you will see message confirming Team City installation along with URL for further configuration (for example: http://localhost:<port defined while installation>).

Team City Configuration

Once TeamCity.exe and JRE/JDK are installed successfully, Team City is now ready for further configurations.

Access the Team City URL and log on to TeamCity using your credentials.
Click the Create project button and Select Manually using the drop-down list.
Enter the Name, Project ID, and Description.
Click Create.
In the Build Configurations section, click the Create build configuration button and select Manually using the drop-down list.
Enter Name and system updates the Build ID accordingly.
Enter Description, if any.
Click Create.
Build is now successfully created and you can proceed to configure Version Control Settings (VCS).
Click the project name on the top of the screen to view Project Settings.
Click the Edit link adjacent to the build configuration created by you.
General Setting screen is displayed.
In the Artifact Paths field, type %env.qualitiareportpath%/**/* => Report.
Click Save.
In the left pane, select Version Control Settings and click Attach VCS root button.
In Type of VCS, select Subversion using the drop-down list.
Enter VCS root name. VCS root ID is populated automatically.
In the URL field, enter the SVN URL up to the parent folder where offline package is uploaded.
Offline Package includes Offline.jar, all the other required files for Offline execution, and XML folder.
Enter SVN Username and Password.
Click Test Connection to test the SVN connection, and click Create.
In the left pane, select Build Steps.
Click the Add build step button.
In the Runner Type field, select Command Line using the drop-down list.
Enter Step name as per your requirements.
In the Run field, select Custom Script using the drop-down list.
In the Custom Script field, enter cd %teamcity.build.checkoutDir% and java -jar <qualitiaofflineJarFileName>.jar
Click Save.
In the left pane, select Parameters.
Click Add New Parameter.
In the Kind field, select Environment variable using the drop-down list.
In the Name field, enter env.qualitiareportpath.
Click Save.

Execute and View Report

Once you are done with Build configuration settings, you can proceed to execute your test cases.

Open the project and build you want to execute from the project's list.
Click the Run button located at the top right corner of the screen.
To check logs, click the in progress builds, and go to build logs section.
Once the build is complete, you can see Build finished at the end in the Build Log section.
In the Artifacts section, click the SummaryReport.html to view the report.

You can even pass arguments and execute same test case with different parameters on different agents simultaneously.

To pass different parameters on different agents simultaneously, access the Build steps section.
Edit the Execute Parameter step.
Add arguments with data followed by SPACE.

Here is an example of how to update the field value along with parameters and the syntax to be used, if the arguments value itself has space.
<path updated in the field>CaptureFailBitMap=False CapturePassBitMap=FalseCreateErrorLog=False sbrowsertype=firefox "xmlPath=f:\\TeamcityOffline
NewExec XMLs" ReleaseNum=2.01 ProjectName=offlinepack LogPath=argreport123
Note: Argument with value consisting space is updated within double inverted comma ("").

Browser not supported