imbus uses cookies to ensure you a better service. By using our site, you agree to our privacy policy.

Continuous Integration (CI) servers are software tools, which execute the CI process in script-controlled fashion, monitor it, collect the results and visualize them on a dashboard.

In agile projects (such as Scrum) new or altered code fragments arise continuously. Every check in of a new or altered code in the central code repository should release an integration run automatically. This process is called continuous integration and it takes place on a CI server.

Quelle: Test in Scrum-Projekten
Tilo Linz: A guide for software quality assurance in the agile world, dpunkt.verlag.



Beitrag (Code Analyse) lesenShow Tools


To write a comment, you need to be logged in.

18.10.2013 by Ernst Softwaretest Consultant at

Hello world, I'd like to introduce myself as moderator of the Continuous Integration (CI) tool category:
My name is Roland Ernst and I’m working as Software Test Consultant at imbus AG based in Germany. In my career, I’ve gained experience in integration and system testing for many years.
It is crucial particularly for the integration test to provide executable and testable actual SW builds at an early time. To achieve this goal, Continuous Integration systems play an important role. Evolving from the beginning based on self-written scripts, there are meanwhile professional tools, both commercial and open source, which are commonly used.
I'd like to encourage you to share your experience: Which CI tools do you use? How do the tools fit into your development and test processes? Which aspects of Continuous Integration are solved well by the tools, and which aren't? What would you like to see from CI tools?