In second step, it runs test methods which were developed in Test Project of Visual Studio vteam # 366 covered all major areas of the project.As a first step, it builds our Visual Studio Solution to ensure there are no compile time errors.Following are main steps involved in this process: Vteam #366 configured TeamCity to run build configuration on every commit in subversion source control.
![teamcity subversion teamcity subversion](https://philippe.developpez.com/articles/IntroductionTeamCity/images/TeamCity17.gif)
Allows configuring many source controls.It allows all kind of steps to configure which are required in continuous integration such as compilation, deployment, running test methods.It allows adding 25 build configuration in free solutions and unlimited steps in each build configuration.It has nice web based user interface to control all operations provided by TeamCity.It is free for average level of use (limited build configurations).We selected TeamCity out of available options due to following reasons:
![teamcity subversion teamcity subversion](https://images2015.cnblogs.com/blog/743314/201606/743314-20160608205306652-1946270931.png)
Following are few of those good tools mentioned here. Vteam #366 researched on the available options and found that there are many tools available. We were allowed to choose any available option which meets all the requirements but does not take too much time to implement. It was also required that all major areas of the application are tested so that each team member knows that last commit did not break anything in the application. It was required that compilation of code, deployment and test methods should run on every commit and all team members located in different locations should be notified about the status of integration process. Client wanted to automate the compilation of projects, deployment on integration server and running test methods.
![teamcity subversion teamcity subversion](https://resources.jetbrains.com/help/img/teamcity/2021.1/NewKotlinDebug.png)
He wanted to ensure that every commit by any developer should be error free. Our Client for vteam #366 has teams in three different countries US, Australia and Pakistan. Continuous integration tools automate the process of integration which can be scheduled multiples times in a day or on every commit of each developer. When integration of source code from developers is delayed there are more chances of problems due to dependencies in the code. Continuous Integration is used to avoid integration hell.