Constant integration means constructing your software every time a developer pushes code. This impacts your testing and requires careful planning and using test automation. CI has a large effect on testing, as it means you are not testing stable applications. On the flip side, the changes you are testing are much smaller. This usually means you've got to adopt another approach to analysing than has been traditionally the case. In this blog, we'll explore CI and examine the challenges it creates for testers. Continuous Integration The foundation and inspiration for CI CI isn't brand new, but it indicated a change from the traditional method of building software. To do CI nicely requires careful coordination and buy from the developers and testers. Once on a time, developers would work individually and in groups on developing their part of their program. Every few weeks they would upload all their code into the server, together with the code from the rest of the teams. The ...