Your browser failed to load CSS style sheets. Your browser or web proxy might not support elliptic-curve TLS

Building network automation solutions

9 module online course

Start now!
back to overview

What Is Continuous Integration?

In spring 2019 Building Network Automation Solutions course we’ll have Kristian Larsson diving into continuous integration and his virtual networking lab product (you might want to listen to the Software Gone Wild episode we did with him to get a taste of what he’ll be talking about). Christoph Jaggi did a short interview with him starting with the obvious question:

What is CI testing and how does it differ from other testing methods?

CI is short for Continuous Integration and refers to a way of developing software where changes written by individual developers are frequently (or "continuously") integrated together into a master branch/trunk, thus continuous integration.

CI testing is about frequently running tests before and after things are merged or integrated such that quality can be upheld and feedback delivered timely to developers. CI testing itself doesn't dictate how you do testing, it's more about triggering tests, so you can use it to run unit tests, integration testing or any other test method you might come up with.

Does CI testing cover all testing needs or is it limited to a subset?

There are probably very few theoretical limits to what can be achieved with CI testing but practically speaking it takes quite a bit of time to write tests. There are certainly ways to speed up the process, for example, for testing of network automation systems, I recommend starting with using virtual routers rather than other types of testing because it usually results in much better test coverage with less time spent on writing tests.

There's a trend today to do testing in production environments through observability tools and the use of deployment techniques like canaries and phased rollouts to mitigate the potential negative effects. I think it's great that we are seeing more of this because testing shouldn't stop in a CI testing environment or the lab but one should also remember that network infrastructure is fundamentally different. Rolling back a web application after a failed deployment is easy because the underlying machine is still operational while botching a network change might mean you lose connectivity, preventing you from rolling back. Networking is different from web applications and as such, we need to apply slightly different testing methodologies. I think we need more rigorous testing early on which is why I have a focus on CI testing with virtual routers.


Want to know more about using CI testing in network automation?

Guest speaker presentations from the network automation course are accessible to course attendees and ipSpace.net subscribers with Expert Subscription who chose the automation course as part of their subscription package.

Please read our Blog Commenting Policy before writing a comment.

No comments:

Constructive courteous comments are most welcome. Anonymous trolling will be removed with prejudice.

Sidebar