Testing can not exist in isolation from the rest of software development processes. The results of testing must be included back to the development. Effectiveness can be increased by automation and centralized monitoring. As an introduction I represent the place of testing in the life cycle of the software, I outline the participants, the testing levels. I mention the traditional methods, as well as the increasingly popular agile methods. I pick out Scrum and extreme programming. In the development of telecommunication systems agile programming applied to everyday industrial practice, what makes the revision of the
integration solutions, evaluating it's statistics. In my thesis I analyze one of those solutions, the Continuous Integration (CI). I review the opportunities provided by the CI, showing the practical application in Jenkins build server. In the CI can be coordinated, scheduled the compiling the source code, running the results,
testing and supervision. I deal the solutions of these tasks with Jenkins, I discuss the additional used plugins. I integrate exterior supporting tools into Jenkins, to increase it's functionality: feedback management, build tools, running of self-developed script, code. I introduce a self-developed Java application, which compares the results of test runs, lists the failed test cases, then diagnoses when the failure reasons are the same of the test cases in other runs.
Then I present static code analyzer tools, and a Python module, with which can be automated various applications.