Continuous integration (CI) and continuous delivery (CD) are a set of best practices designed to enable development teams to create, modify, improve, and deliver product changes more frequently and with less errors. The entire process is usually called the CI/CD pipeline. Testing as part of Continuous Integration (CI) and Continuous Delivery (CD)One of the most important parts of CI/CD is testing. Testing also needs to be continuous by definition. Remember, our concern is making sure we deliver quality applications to our stakeholders. Continuous testing will consist of running automated regressions, functional tests, unit tests, and performance tests. These tests need to be executed as part of the CI/CD pipeline.CI/CD tools such as Jenkins, CircleCI, AWS CodeBuild, Travis CI, Atlassian Bamboo, or others are the tools of choice today for CI/CD. All allow DevOps engineers to incorporate automated testing. Additionally, services like SauceLabs allow for CI/CD to be run at high scale and with enterprise level SLAs. And there are lots of other innovative tools that should be in your testing quiver - tools like scriptworks.io for using a low-code approach to creating your Selenium scripts.However, today, I want to talk about taking CI/CD automation to the next level by introducing visual process design into your CI/CD toolkit mix. WARNING - Like any technology, this is not for everyone and not for every situation. For many of you, this will be overkill and you may scratch your heads thinking “why do I need this.” You may not need it.So, who should be interested in adding visual CI/CD process Automation to their current CI/CD process? Here are some of the characteristics to look out for to see if your software project should use visual process automation as an integration/extension of your CI/CD tooling:
