The subject of Continuous Integration (CI) does not have to be linked to DevOps processes, as it is an independent activity by itself. CI promotes automated development into a testable package, which can then perform automated testing. The primary starting point for such self-testing code is Test Driven Development (TDD), so that you define the test cases and test scenarios beforehand or in parallel with the development activities of such types of testing--unit testing, integration testing, system testing, and stress and performance testing. CI is usually implemented as a separate CI server, which is integrated with your source control. The following types of testing, for example, can be configured to run as Automated Tests: unit testing, integration testing, system testing, and stress and performance testing. CI is usually implemented via a separate CI server that is integrated to your source control. Visual Studio Team Services (VSTS) is one of the good CI servers around, which not only integrates with the MS Team Foundation Server (TFS) source version control, but also with Git. It also supports multiple build and testing agents, which are available on multiple platforms--Windows, Mac, and Linux.