TeamCity

TeamCity is a Java-based build management and continuous integration server from JetBrains. You need to install TeamCity in order to execute offline package using TeamCity.

TeamCity Installation

Follow the below-mentioned steps to install TeamCity.

1. Download Team City and JRE 6,7/JDK 1.6,1.7.
2. Install JRE 6, 7/JDK 1.6, 1.7.
3. Right-click the Team City setup.exe and click Run as Administrator.
4. Follow the on-screen installation steps.
5. Post-Team City installation, install TeamCity agent as well.
6. Navigate to services.msc and stop TeamCity Agent service.

7. Launch the Command Prompt as administrator and execute the agent.bat file.
   

   Please note that TeamCity needs to be started using agent.bat command only. If you use TeamCity as a service, you won’t be able to see the browser during test case execution.\

8. Once the setup is complete, access TeamCity URL (http://localhost:<port> defined when installation).
   If Client and Server are on two different systems then the user should run the client manually using the command prompt with the administrator privileges (that is Run as Administrator).

TeamCity Configuration

To configure TeamCity:

1. Access Team City URL. (http://localhost:<port>)
2. Create a new project.
3. Under the Build Configurations section, click Create build configuration.
4. Enter Name.
5. Enter Artifact Paths as:- QualitiaReport/**/* => Report.
    Please do not update any other field in this section.
6. Click, VCS Settings > create and attach new vcs root.
7. Select Type of VCS as Subversion.
8. In the URL field, update SVN URL till parent folder location where XML's and Offline Package is uploaded.
9. Enter SVN credentials in the Username and Password fields.
10. Click Test Connection to test SVN connection.
     Please do not update any other field in this section.
    
11. Click Add Build Step.
12. Select Runner Type as Command Line.
13. Select Execute Step as per user understanding.
14. In the Run drop-down list, select Executable with parameters.
15. In the Command executable field, enter %system.teamcity.build.workingDir%<followed by Offline Package path on SVN>.
16. Add another line in the Command executable field as QualitiaOffline.exe.
17. Click Save.
    This will execute the offline package.
    
18. Click Build Parameters.
19. Click Add new Parameter.
20. Select Kind as Environment variable from the drop-down list.
21. Enter Name as env.qualitiareportpath.
22. Click Build Step.
23. Click Add Build Step.
24. Select Command Line from the drop-down list.
25. Enter the build name as per user understanding.
26. From the Run drop-down, select Custom script.
27. Enter the Custom Script field as follows:
    xcopy /I /Y /E %env.qualitiareportpath%\* .\QualitiaReport.
    
28. Click Save.

Execution and Reports

Once configured successfully, you can proceed for executions using TeamCity.

To execute your test cases in TeamCity:

1. On the top right corner, click Run.
2. Click Build in Progress and go to the Build Logs section to check the logs.
3. Once the build is complete, the user would see Build Finished towards the end of the logs.
4. Click the Artifacts link to see the report in the browser.

5. Click SummaryReport.html to view the report.
   
   

   User can even pass arguments and execute the same TC with different parameters on different agents simultaneously.

   
   

6. To adjust settings, navigate to the Build Step section.
7. Edit the Execute Parameter step.

8. Following the updated value in the field, add the argument with respective 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=False CreateErrorLog=False sbrowsertype=firefox "xmlPath=f:\\TeamcityOffline\\NewExec XMLs" ReleaseNum=2.01 ProjectName=offlinepack LogPath=argreport123

    Argument with a value consisting space is updated within ‘ “ ‘ (double quotes). Qualitia doesn’t recommend changing these values as changing following values has a major impact on the offline execution.

   ToolName=QTP and DryRun=False.