Automation Testing with CI/CD

  Integrate Cypress Automation Tests with Jenkins With Jenkins, First you need to do an initial set up and make sure you have Java installed for Jenkins on your PC. Open Jenkins  http://localhost:9090/   to  login with your credentials  and create a Freestyle project for Cypress with name “Cypress” like shown below Your  Freestyle project  configuration is like this below. Since it's a local project you can ignore the "Git" option for now. Click on "Apply" and "Save" button. you are good to go. Click on "Build Now" to run the Cypress tests   Cypress GitHub Repo:   Cypress-Repo Happy Automation Testing Guys :) !

  Integrate Puppeteer Automation Tests with Jenkins With Jenkins, First you need to do an initial set up and make sure you have Java installed for Jenkins on your PC. Download the "Jenkins.war " file  with name “Generic Java package (.war)” from  https://www.jenkins.io/download/  and copy to the project root folder. Open VS code and navigate to your project folder and copy the "jenkins.war" file into the project root folder. Open VS code and navigate  to your project folder and copy the "jenkins.war" file into the project root folder and run the command  " npm run start-jenkins-server"  to start Jenkins on port 9090 I open another VS Code window and run the command "npm start" to start my web application on localhost:3000 My application looks like this on Localhost:3000 below. Note: Your Frontend and Backend App should be running   Open Jenkins http://localhost:9090/  to login with your credentials and create a Freestyle project for ...

In this blog post, I have taken Playwright tests to integrate with CI process using Bitbucket and GitLab . A typical diagram of CI/CD from a QA stand point below When we say Continuous Integration , It means an Automated process which easily manages frequent releases. It is a process which kicks off the pipeline by detecting, pulling, building the changed source code and automation testing on the fly for the changed source code of a product. From the above diagram I have taken a typical monolithic project where automation testing is performed here on both Localhost/Dev environment and staging environment.  In some projects we directly target the Staging/Pre-Prod environment only as the developers perform unit testing on their DEV environments. The idea here is to create an automation test framework and create a repository for the test code. Run these tests on headless mode on your CI tool like Jenkins, GitLab, Bitbucket etc.. as a part of continuous integration. When it...