We have a wdio-based automation project that does end-to-end functional testing. We use CircleCI as the CI/CD tool to run automation regression. When setting up a project with CircleCI, we need to enter all configuration details in the config.yml file under the .circleci folder. Earlier, we only had staging regression and prod regression jobs and their respective workflows in the config.yml file. As mentioned in this article, we also started doing screenshot testing for our application. With time, our configuration file expanded and became cluttered, accommodating various workflows like staging sanity, staging regression, prod regression, performance score

Continuous Integration(CI) and Continuous Deployment(CD) play an essential role, especially when working in a team. In our project, we are following Agile methodology & we do multiple releases during the week. To ensure that the build is generated without any error, CI/CD proves advantageous. "There should be two tasks for a human being to perform to deploy software into a development, test, or production environment: to pick the version and environment and to press the “deploy” button." David Farley For every feature, we create a separate pull request. Every time on commit, CI automatically triggers

Devising ideas to writing code and finally deploying finished products can be quite tedious at times. You need to handle many things beyond just writing the code. But what if you could take some of this work off your shoulders? Well, this is where GitHub Actions really shines. In this article, we will cover how to create a workflow that will trigger the deployment using GitHub Actions into GitHub Pages whenever there is any change(s) found in the master branch of the repository. Lets go through some fundamentals 👨🏻‍💻 Already know these fundamentals? You may then skip directly to action

Automating test scenarios have become an integral part of any successful product release. We have selenium automation suite covering important feature flows. We run our test suite on a weekly basis as a regression health indicator. We deployed Jenkins, a CI/CD tool, to build, deploy and automate our test suite. In this article, we will explain the steps to set up Jenkins on our Ubuntu machine and how we overcame the various challenges we faced. Background We collaborate with a USA based large CRM SaaS application to build new features. We also enhance the application. We use Kanban Agile