Most organizations make use of Continuous Integration (CI)* tools like Jenkins, Bamboo, or CircleCI. Developers use Continuous Integration to automate steps of the development process. This results in faster feedback on their work. Testers need to keep up with these developments. They need to know what happens with Continuous Integration and which influence this has on testing (e.g. which test can be executed at which level). Proper understanding of Continuous Integration allows testers to work more efficiently. Next to that, testers often need to use Continuous Integration tooling to execute automated tests.
In Short, Continuous Integration compiles the changes in software and evaluates these changes. After an alteration of code the change in software is stored in a version managementsystem. Subsequently this alteration automatically gets compiled, (unit)tested and quality checked. This results in a Continuous Integration of the software with a corresponding quality control.
* Continuous Integration is a development practice that requires developers to integrate code into a shared repository several times a day. Each check-in is then verified by an automated build, allowing teams to detect problems early.
The following topics are discussed in this one day training:
The participants get to know the world of Continuous Integration through a mix of theory and practical exercises. The tool used in the training is Jenkins. At the end of the day there will be a short introduction to Continuous Delivery (CD).
The training is designed for test professionals with little or no experience with Continuous Integration.
Enroll for this course Introduction CI/CD.