This list includes automation test sites that provide some unique features that other sites do not have. As a result, you can combine everything to get a complete profile of different types of automation skills.

: You can practice various streams for online shopping on this fake e-commerce site. If you're working on a project where you need to practice various stream types, this is the site you need. You can practice

: This DemoQA contains many of the typical features found on most websites, and it is designed well to practice test automation, so that you can see how to approach each of the different things you may find, like a list that is ordered with drag and drop, user inputs of different types, and so on

: A collection of free APIs for use by developers & QA's. This includes APIs for using data, creating applications, and more.

: This repository contains our Sauce Labs sample app. You can use it locally or in our Real Device Cloud as a sample app for test automation.

: This is a fantastic website to practice for the FinTech industries. This Angular Banking Site is a simple banking website written in Angular. There are transactions listed, as well as login behaviors. Transactions list, deposits, and withdrawals are also shown.

Testing sites are always a must, even for courses, workshops, webinars, testing new tools, and more....

Websites to Practice Automation Testing (UI, Mobile & API)

The Amazon Elastic Container Registry (ECR) has been a popular option for many developers and DevOps teams when it comes to creating and deploying Docker images. However, GitHub Container Registry (GHCR) is a great choice if you're seeking an alternative to ECR. GHCR enables you to manage and store your Docker images right inside GitHub repositories. In this blog post, we'll look at utilising GitHub Actions to create and upload Docker images to GHCR.

Your current GitHub operations are seamlessly integrated with GitHub Container Registry. It makes use of GitHub Actions' strength to let you automate the creation, testing, and distribution of your Docker images. You may manage and interact with your team more easily by using GHCR to maintain your source code and Docker images in one location.

Before we dive into the steps, make sure you have the following:

A Project with Dockerfile in the root level

To get started, navigate to the root directory of your GitHub repository and create a new directory called 

. Inside this directory, create a new file named 

. This file will contain the configuration for our GitHub Actions workflow.

Every push to the main branch initiates the execution of this workflow. It creates the Docker image, pushes it to GHCR with the supplied image name and tag, and logs in using the GitHub token.

 with the desired name for your Docker image.

 file and commit it to your repository. Push the commit to trigger the workflow.

To monitor the workflow, navigate to the "Actions" tab in your GitHub repository. You should see a workflow named "Build and Push Docker Image" running. Click on it to view the workflow's progress.

When the procedure is finished successfully, select the "Packages" tab in your repository. Your Docker image will be accessible under the GitHub Container Registry area. To view the available tags and further information, click on it.

In this blog post, we looked at utilising GitHub Actions to create and upload Docker images to the GitHub Container Registry. You may streamline your development and deployment procedures and simplify your Docker image administration by using GHCR. You may improve your CI/CD workflows and boost the effectiveness of your software development lifecycle with GitHub Actions' automation features.

So give it a shot and experience the potential of GitHub Container Registry for your hosting needs for Docker images. Happy building!

Note: GitHub Container Registry is an evolving service, and it's recommended to refer to GitHub's official documentation for any recent updates or changes to the service.

If you enjoyed this article, please click the 

 button and share to help others find it!

In this blog post, we explore an alternative to Amazon Elastic Container Registry (ECR) by leveragin...

AWS ECR Alternative - How to Build and Push Docker Images to GitHub Container Registry with GitHub Actions

Before we start, let's talk about what cucumber is and why we use it here

Cucumber is a tool that supports behavior-driven development (BDD). It runs automated acceptance tests written in BDD format. Cucumber provides a way to write tests that anybody can understand, regardless of their technical knowledge. It explains test steps and application behavior in simple English using the Gherkin language.

Let's add cucumber to cypress and automate a simple login flow

There are a few prerequisites before we can start installing cucumber, you need to have these tools to initiate project setup.

Type the below command on the terminal to install cucumber

The next step is to set the configurations in 

 inside the root directory of your project and specify the location of step definitions as follows

As we are finished with the basic configuration, we are now ready to write up the script. We will be using 

https://opensource-demo.orangehrmlive.com/

 for this purpose and automating the Login test case for demonstration.

 to run cypress. You can directly open cypress Launchpad from here

Now we can run the below command to open cypress UI

 from your feature files inside the Spec Explorer

I hope you found this article helpful. Follow the above steps and run your first test case with cypress and let me know how it went in the comments.

Link to 

As not long ago we were introduced to Cypress v10 with breaking changes. The process of installation...

How to set up Cucumber in Cypress 10?

The first step is to sign up for an API key on the 

 website. Once you created an account, you can generate your API token and start using it in your automation framework.

To use ChatGPT API, you will need to install and import OpenAI package to make requests to the OpenAI API. You can use any programming language of your choice like JavaScript or Python to access their API.

I have chosen to use their Node JS option where we will be creating a node script to call the API and generate Cypress test cases. Once we have generated the script we will then use Cypress to run and test the AI-generated test case.

Within your Project, Create a new file (call it how you like) Im calling it 

 . To use ChatGPT API, you will need to install and import OpenAI package to make requests to the OpenAI API. Run 

Next, you will need to initiate configuration which will take in an argument, here you will add your apiKey

We will then need to initiate the openai that will take in the configuration we create above which will authenticate the user.

Now we can use one of many functions from openai, in this case, we will be using 

 which takes multiple arguments as been below. After playing around I feel these arguments suited the type of response I was looking for.

 , we should see a response in the terminal like this.

Now let's take it to the next level, We can see that we can give the AI instructions and it will give us the response with the code we are looking for.

We can make it more robust by we fill a form that takes in the 

 to generate the script.
So Create a json new file (call it how you like) Im calling it 

To use this, we will need to modify some of the code we created above.
In the below code, we are importing the 

 npm package and the .json file we created. In our API call, we then modify the 

 to take in the data from the .json file and also we are using the 

 function to create a new file with the name provided by the .json file and save it in the 


If you enjoyed this article, please click the 

Vidya

In this article, I will be showing how to Integrate ChatGPT into Cypress and generate test scripts automatically just by filling out a form. It will create a script and save it into the right directory and we are good to run the script.

How to Integrate ChatGPT into your automation framework

If you want to integrate Jira into your automation framework, you’re in the right place. This post will demonstrate how to integrate Jira into Playwright. This is just one scenario that we will be covering which is when a test run has failed, raise a Jira issue for each of the failed tests but there are many other scenarios that can be covered.
Note -  this concept can be used in another automation framework not only Playwright.

 - you may need permission to access this section of Jira

 any issue in the project that has a bug type and the status not in Declined, Done, or Deployed, and the summary name extracted from the webhook payload

 to only create a New Bug ticket if the look-up result is 

, this way you don’t have duplicate issues in your Jira.

Create a Script to call the webhook in your automation framework, In this example, I will be using Playwright.

In Playwright when a test run has been completed, there is an Option to output the results in JSON format.
With this, we can create a function to loop through the JSON file and retrieve any failed scenarios. We then create a new array and push the data into it so we can be used later on

In this function, we will be calling the webhook via Axios but you can choose any other request liberty. We then use the information from 

Once you have constructed the script, you call this script once the test run has been completed. If you are using Playwright, you will need to configure it to 

See below for how to populate your Jira issue with the Payload you send from your automation framework. 

This post will demonstrate how you can integrate Jira into your automation framework to raise a bug ticket when a test failed in your test run. In this example, we will be using Playwright.

Creating a Jira issue when a test run fails using Playwright

The NVM (Node Version Manager) is a shell script that is used to install and manage Node.js on a Linux-based system. Homebrew is used to install NVM on macOS.

This guide will show you how to install NVM on your macOS machine and manage

Install Homebrew (You must have admin privileges)

If your system already has a node installed, uninstall it first. My system already has installed node via Homebrew. So uninstalling it first. Skip if not already installed.

Update the Homebrew package list and install NVM.

Next, create a directory for NVM at home.

Now, configure the required environment variables. Edit the following configuration file in your home directory

Next, load the variable to the current shell environment. From the next login, it will automatically loaded.

That's all. Your macOS system now has the NVM installed. Continue to the following step to install Node.js versions using nvm.

First, let's see what Node versions are available to install. By typing:

Now, you can install any version listed in the above output. You can also use aliases names like 

After installing you can verify what is installed with:

If you have installed multiple versions on your system, you can set any version as the default version at any time. To set node 14.X as the default version, simply use:

Similarly, you can install other versions like Node 12, 15, and 18 versions and switch between them.

We are going to go through NVM - Node Version Manager and how to setup via Homebrew

How To Install NVM on macOS with Homebrew

Cypress basic commands are listed below in no particular order  −

Get single or multiple elements by the locator.

Get the first elements of a particular locator.

It clicks an element in Document Object Model (DOM).

It obtains an element having a specific text. The element can have more than the text and still match.

It is used to create an assertion and is an alias of .should ().

It removes the value from textarea or input.

It removes the browser cookies from an existing domain and subdomain.

It iterates through an array having the property length.

It obtains the descendant elements of a particular locator.

It is used to create an assertion and is an alias of .and ().

It obtains a particular browser cookie by its name.

If you feel like there is a command that should be on this list, please leave a comment below!

Cypress is a fast, easy and reliable testing tool for anything that runs in a browser. It’s becoming more popular choice of a tool than any other. I have collected some of the most common commands I use on a daily bases.

Cypress most common commands

Notification is one of the key aspects of a pipeline. You don't want to keep looking at Jenkins screen to know the status. Rather you want to continue doing the next work and get an upate when the pipeline is completed.

In this article, we will learn how to use Jenkins Pipeline plugin to notify Microsoft Teams channel about pipeline status.


 
From your Jenkins dashboard navigate to 

 tab. Locate this plugin by searching for "Office-365-Connector".

jenkins-plugin-cli --plugins Office-365-Connector:4.17.0

2. Configure MS Teams Channel to send Jenkins Notification

Create a Team channel for your notification to appear in 

Now, go to that channel, and from the top-right corner, click on 3 dot arrows and select 

Create a Name for the connection and click "

You can configure it in two ways; Options or in a Stage 



 at the top, where you will be notified about failure and success results at the end of the pipeline

Create a secret as a text in Jenkins and called it `webhook` and add the Webhook URL that you got from 

This will notify channel for listed statuses

 – Notify if the current build has failed

 – Notify if 2 or more consecutive builds have failed

 – Notify if the current build is successful

 – Notify if, after failed builds, the current build got successful

notifyAborted – Notify if the build is aborted by the user

 you will be notified when this stage is 

In this article, we will learn how to use Jenkins Pipeline plugin to notify Microsoft Teams channel about pipeline status.

How to send notification to Microsoft teams from Jenkins

We will be discussing a topic that has been talked about when it comes to E2E testing. It's vital to cover complete E2E testing, even if the user receives an email confirmation.

In this example, we will be looking at the forgot password feature on tes.com.
We will automate a test case to verify that the user receives an email to reset their password. We will be checking elements such as the From, Subject, and Body of the email.

The good news is that MailSlurp is a free API that lets you create real, randomized email addresses on demand. It also lets you send and receive email programmatically

Create an Inbox to get an email & Inbox ID (save it for later)

This will generate the cypress folder where we can create a spec file



 to 30 seconds, allowing our tests enough time to wait for emails to arrive. We will also modify the Cypress browser's viewport dimensions.

: Create a Spec file
Next, create a test spec in with the following folder structure:

let's write our first test in the above directory:

 with your mailslurp inbox id and email address 

We will be discussing a topic that has been talked about when it comes to E2E testing.  It's vital to cover complete E2E testing, even if the user receives an email confirmation.

Test emails with Cypress.io 

Cucumber is a tool that supports behavior-driven development (BDD). It runs automated acceptance tests written in BDD format. Cucumber provides a way to write tests that anybody can understand, regardless of their technical knowledge. It explains test steps and application behavior in simple English using the Gherkin language. 

Cucumber is an important testing tool for the following reasons:

No longer need to write test scripts in multiple languages such as javascript, Python, Java, etc.

It can be integrated with many Automation tools such as Cypress, Selenium, Ruby on Rails, and other web-based testing tools.

Run the following command to install Cypress locally:

Run the following command to install the Cucumber for Cypress package:

 Add the configuration Cypress environment files

In the spec files extension parameter in the 

 file, make sure to point to the feature files:

Let’s first write this test by just using Cypress:

), enters the username and the password and clicks the “

In Cypress, users can group multiple commands into a single custom command by creating a file called 

Now, use the custom command in the tests:

The above code is written using Cypress. Now, on using Gherkin for Cucumber, the code goes as follows:

I login’, ‘the url is {word}’, and ‘I’m logged in

. So create 3 step definitions. Create a Javascript file inside a directory named as the feature file (

Once this code runs, Cucumber will convert it into Cypress commands. And, that’s how it works.

Till now, we have written all the Cypress test scripts directly in the JavaScript files, but with the integration of Cucumber, the test structure will change, and now the entry points will be the Cucumber feature files.

How to set up Cucumber with Cypress?

In this post we are going to cover a top that is highly important to take your cypress project to the next level.
I will be going to show you how to run cypress in a Jenkins pipeline via Docker container.

Docker installed & configured on your local machine

:
We will need to create some volumes for Jenkins Docker container

 command to pull down the Jenkins Docker image and serving the Jenkins App on 

If it's your first time running Jenkins, It will prompt you with Unlock Jenkins Page where you will need to enter an admin password. To retrieve this we can find it in the logs. It looks like this: 

You'll be requested to establish a user and log in for future sessions when you go passed the 'Unlock Jenkins' screen. Continue by creating your selected user.

The 'Customize Jenkins' page will appear after that. Continue by selecting 'Install Suggested Plugins'.

These are examples, you will need to modify them for your own project 

Docker file is optional as we can pull down the cypress docker image from Jenkinfile directly 

In this post I'm going to show you how to run Cypress in a Jenkins pipeline (via Docker).

Integrate Docker  & Jenkins in to Cypress

Postman, akin to a Swiss army knife, offers a user-friendly interface and a comprehensive suite of features tailored for API testing. On the other hand, Charles Proxy serves as your vigilant watchdog, enabling deep network traffic analysis and debugging.

In this blog post, we embark on a journey to explore the synergies between Postman and Charles, uncovering their respective strengths, collaborative potential, and how they can elevate your testing prowess to new heights. Join me as we navigate through the realms of API testing, armed with the formidable capabilities of Postman and Charles, empowering you to deliver superior software with confidence and precision.

Charles Proxy and Postman are both popular tools used by developers and testers for API testing and debugging, but they serve slightly different purposes and have different feature sets.

Charles Proxy is primarily a web debugging proxy tool. It allows you to intercept and inspect HTTP and HTTPS traffic between your computer and the internet. With Charles Proxy, you can monitor network traffic, view HTTP requests and responses, set breakpoints to intercept requests, manipulate requests and responses, and simulate slower network connections. It's commonly used for debugging and analysing how web applications work, diagnosing issues with APIs, testing web services, and security testing.

Whereas Postman, on the other hand, is an API development environment. It provides a user-friendly interface for building, testing, and documenting APIs. With Postman, you can create requests using various HTTP methods (GET, POST, PUT, DELETE, etc.), set headers, add request parameters, organise requests into collections, and automate testing with scripts. Postman also offers features for mocking APIs, generating API documentation, collaborating with team members, and running automated tests. While Postman does allow you to view request and response details, it's more focused on API development and testing workflows rather than low-level network debugging like Charles Proxy.

Now let’s take a deeper dive into the pro’s and con’s of each tool.

Charles Proxy provides detailed insights into HTTP and HTTPS traffic between your computer and the internet, allowing you to monitor requests and responses in real-time.

2. We can manipulate the request and responses.


It enables you to intercept requests and responses, modify headers, tweak payloads, and simulate various network conditions, which is extremely useful for debugging and testing purposes.


Charles Proxy allows for SSL proxying, meaning it can decrypt and inspect encrypted HTTPS traffic, giving you full visibility into encrypted communication, which is crucial for debugging secure applications.

4. We can use Charles across different platforms

 (not only for web, but even devices such as phones!)

5. We can throttle and create different bandwidth simulations.


You can simulate different network conditions such as slower connections, dropped connections, or limited bandwidth to test how your application performs under various network scenarios.


 While Charles Proxy offers a free trial, it's ultimately a paid software, which might be a deterrent for some users, especially those who have budget constraints.


 For beginners, Charles Proxy can have a bit of a learning curve, especially when it comes to understanding all its features and how to effectively use them for debugging and testing. But not to worry, I can create an easy step by step guide to get you all set up with Charles!


4. Running Charles Proxy alongside other applications can consume significant system resources, 

especially if you're dealing with a large amount of network traffic or SSL decryption.

While Charles Proxy is excellent for inspecting and manipulating network traffic, it lacks the comprehensive API testing features found in dedicated tools like Postman, such as automated testing, request collections, and scripting capabilities.

Overall, Charles Proxy is a powerful tool for network debugging and analysis, but it may not be suitable for all use cases, particularly those requiring extensive API testing capabilities or those with limited budgets.

Well, firstly Postman provides User-Friendly Interface.

1. Postman provides a clean and intuitive interface,

 making it easy for developers to create, test, and manage API requests without requiring extensive technical knowledge.

2. Us, testers can carry out comprehensive API Testing.


 Postman offers a wide range of features for API testing, including support for various HTTP methods, setting headers and parameters, handling authentication, organising requests into collections, and running automated tests.

3. We can use postman to collaborate together!


 Postman enables team collaboration by allowing users to share collections, workspaces, and environments, facilitating better communication and coordination among team members working on API projects.


Postman provides scripting capabilities using JavaScript, allowing users to automate tests, set up pre-request and post-request scripts, and perform data-driven testing, thereby saving time and improving efficiency.


 Postman allows you to create mock servers, which simulate API responses without needing the actual backend implementation. This is useful for frontend developers to start building applications before the backend is fully developed.


 Postman lets you define environments with variables, making it easy to switch between different environments (e.g., development, staging, production) without modifying individual requests.

However, lets now see the limitations of Postman:


 While Postman allows you to inspect request and response details, it's not as robust as dedicated network debugging tools like Charles Proxy for analysing low-level network traffic.


 While the basic features of Postman are straightforward to use, mastering advanced features such as scripting and automation may require some learning for users who are new to API testing and development. (Not to worry, I will have you covered!)

Postman and Charles – the dynamic duo revolutionising API testing and development. 

I’m Pirasanth — but call me PJ.

I love to program, write automation scripts, travel, and lift heavy things.

Cypress.io

Webdriver.io

Cucumber.io

K6.io

Appium

Selenium

React JS

Node.js

Puppeteer