Automation Testing with CI/CD - Playwright Automation Tests with Jenkins

Integrate Playwright 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:8080/ to login with your credentials and create a Freestyle project for Playwright with name “Playwright” like shown below

First Click on the "New Item" as shown below




After clicking on "New Item" you will see a screen like below



Enter the name as "Your desired name" as I've entered as "Playwright" for now. Select Freestyle project and click "OK" button. You will be navigated to the "Configure" section



Give your description in the text box "Description". Select "Git" as the "Source Code Management" option as we are using this git repo: Git Repo

Give the access to your credentials for git if it is a private repo. I've used a public repo so the credentials are not needed.

Enter your branch as "main" as I'm using the master branch. You can use your own branch other than master branch if specifically needed.


Fill in the "Build" step like below


Fill in the "Execute shell" with commands like shown below.



Click on "Apply" button like mentioned above. You will see a screen like this below with your settings saved.

Click on "Save" button finally!!!


Now, you are now on your project page. Click on "Build Now" to execute your playwright automation tests



Check your console output 







Happy Automation Testing Guys :) !




 




Comments

Post a Comment

Popular posts from this blog

Automation Testing with CI/CD - Playwright Automation Tests with AWS CodeBuild

Image
Integrate Playwright Automation Tests with AWS CodeBuild In this blogpost, We will integrate playwright automation tests with AWS CodeBuild. What is AWS CodeBuild?  AWS CodeBuild is a fully managed continuous integration service that compiles source code, runs tests, and produces software packages that are ready to deploy. With CodeBuild, you don’t need to provision, manage, and scale your own build servers.  CodeBuild scales continuously and processes multiple builds concurrently, so your builds are not left waiting in a queue.  First of all, sign up with AWS to create an account. Login with your credentials to  https://aws.amazon.com/ You will see a home page like this below Now, Type " CodeBuild " in your search bar at the top and hit enter! You will be navigated to CodeBuild section like below Old (Please do not follow below screenshot) Now, Click on Create project button Old (Please do not follow below screenshot) You will be navigated to Create Build Project...
Read more

Automation Testing with CI/CD - Playwright Automation Tests with Azure DevOps Pipeline

Image
  Integrate Playwright Automation Tests with Azure DevOps Pipeline In this blogpost, We will integrate playwright automation tests with Azure DevOps pipeline. First of all sign up with Azure Devops to create an account. Login to  https://dev.azure.com/ Create an organisation first. I have created an organisation with name “jaykishore999”. You can create with your own name. If you have a GitHub account already then you can login using your GitHub account as well. Click on " + New project " Click on " Create " button Hover on to the "Pipelines" on the left side nav bar and click on the option "Releases" Click on "New Pipeline" button  Click on the "Empty job" Click on " Add an artifact " on the left panel Click on " GitHub " and click on "+ New" button to authenticate with GitHub Click on " Authorize using GitHub " and select a repository you want to execute tests from the GitHub Select ...
Read more

Automation Testing with CI/CD - Playwright Tests with Bitbucket and GitLab

Image
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...
Read more