The Next Wave of CI/CD - Designing and Automating Visual CI/CD Processes
Posted: Sun Dec 22, 2024 5:31 am
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 fewer errors. The entire process is commonly referred to as the CI/CD pipeline.
Testing in Continuous Integration (CI) and Continuous Delivery (CD)
One of the most important parts of CI/CD is testing. Testing should also be continuous by definition. Remember, our concern is to ensure that we deliver quality applications to our stakeholders. Continuous testing will consist of automated regressions, functional tests, unit tests, and performance tests. These tests should be executed as part of the CI/CD pipeline.
CI/CD tools like Jenkins , CircleCI , AWS CodeBuild , Travis CI , Bambou d'Atlantide or others are the tools of choice today for CI/CD. All of them allow DevOps engineers to integrate automated testing. Additionally, services like SauceLabs allow CI/CD to be managed at scale and with enterprise-level SLAs. And there are many 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 to you about philippines phone number whatsapp automating CI/CD by introducing visual process design into your CI/CD toolset. WARNING - Like any technology, it is not for everyone or every situation. For many of you, this will be overkill and you may be scratching your head wondering "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 characteristics to look for to determine if your software project should use visual process automation as an integration/extension of your CI/CD tool:
Multi-tenant - You are using a multi-tenant SaaS application
Stakeholder Involvement - You have customers or partners who need to be involved in the design and quality control process and code delivery
Customization - Your application allows customers to customize it and therefore your Selenium functional tests will tend to grow and change frequently (IMHO this is perhaps the main reason to use visual design of CI/CD processes).
Manual Approval Steps - You may need manual approval steps for certain types of tenant updates, ISO and regulatory compliance, or due to stipulations in customer contracts
Testing in Continuous Integration (CI) and Continuous Delivery (CD)
One of the most important parts of CI/CD is testing. Testing should also be continuous by definition. Remember, our concern is to ensure that we deliver quality applications to our stakeholders. Continuous testing will consist of automated regressions, functional tests, unit tests, and performance tests. These tests should be executed as part of the CI/CD pipeline.
CI/CD tools like Jenkins , CircleCI , AWS CodeBuild , Travis CI , Bambou d'Atlantide or others are the tools of choice today for CI/CD. All of them allow DevOps engineers to integrate automated testing. Additionally, services like SauceLabs allow CI/CD to be managed at scale and with enterprise-level SLAs. And there are many 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 to you about philippines phone number whatsapp automating CI/CD by introducing visual process design into your CI/CD toolset. WARNING - Like any technology, it is not for everyone or every situation. For many of you, this will be overkill and you may be scratching your head wondering "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 characteristics to look for to determine if your software project should use visual process automation as an integration/extension of your CI/CD tool:
Multi-tenant - You are using a multi-tenant SaaS application
Stakeholder Involvement - You have customers or partners who need to be involved in the design and quality control process and code delivery
Customization - Your application allows customers to customize it and therefore your Selenium functional tests will tend to grow and change frequently (IMHO this is perhaps the main reason to use visual design of CI/CD processes).
Manual Approval Steps - You may need manual approval steps for certain types of tenant updates, ISO and regulatory compliance, or due to stipulations in customer contracts