Deploying a Selenium grid on Docker Swarm

Objective: To be able to run more than 10 browsers and using multiple machines(Server1,2).

Docker Swarm requires few ports to be open for it to work. These are : – 

-TCP port 2377. This port is used for communication between the nodes of a Docker Swarm or cluster. It only needs to be opened on manager nodes.
-TCP and UDP port 7946 for communication among nodes (container network discovery).
-UDP port 4789 for overlay network traffic (container ingress networking).

Install Docker
First install docker on all 2 Server 1,2

Then add the ubuntu user to the docker group, so we don’t need to use sudo everytime we use the docker command

On Server 1

Now docker swarm is ready and nodes can connect to it, ssh into the Server 2 grid machine and run the following command
On Server 2

Run the following command to deploy docker swarm — : – 

To view the status of the docker swarm : –

To shut down docker swarm

To debug a specific container

To leave docker swarm, type the following command both on manager node and worker node

Slides –
Instructions –
Grid Yaml –


321 total views, 18 views today


Integration of Protractor Beautiful Test Reports

Test Reporting in the Software testing is an essential part.  Finding a good reporting is an always very tedious task. In this tutorial, We will learn how we can integrate the ‘Protractor Beautiful Reporter’ –

Why we choose this.
Normal Jasmine reporter is very simple and not much screenshot friendly. This plugin has following features which makes it more suitable for Reporting for Protractor / Angular based Projects.

  • Get attached Screenshots
  • Selenium & Browser’s Logs (only for Chrome)
  • Full Stack Trace (with suspected line highlight)
  • Screenshot only on failed spec.
  • Test Search
  • Filters (can display only Passed/Failed/Pending/Has Browser Logs)
  • Inline Screenshots
  • Details (Browser/Session ID/OS)
  • Duration time for test cases (only Jasmine2)

Note  – If you are using the jasmine 2(Jasmine 1.x: No longer supported), It can be integrated very easily with two steps.

Installation  – 

In your protractor config file  e.g protractor-config.js

Please note that the screenshots are generated are in  /tmp/screenshot directory.

If you want to have screenshot in sub folder  –

Screenshots Subfolder (optional)

You can store all images in a subfolder by using screenshotsSubfolder option:

Reports –  


Normal Test Results of Passwd Testcases – 

Support of logs  : – 

Failed logs and screenshot results

Read more at –

We have used it for a while. It far better than “Jasmine2HtmlReporter“. which lags in UI and some features.

Note: Make sure you delete the previous build folder of Junit else. It will combine your builds in one report.

Thanks for reading ! 🙂 If you enjoyed it, hit that share button. Would mean a lot to me and it helps other people see the story.

378 total views, 15 views today


Web Automation with Machine Learning –

In this tutorial, we are going to learn about tool that is an only ML-driven test automation service that automatically maintains tests and identifies regressions for you.

In this tutorial, we are going to create an end to end test cases in and make them run in platform.

615 total views, no views today


Software Testing Lectures - Understanding Bug Cycle

In this tutorial, We are going to discuss the Software Testing Lecture and try to understand the Bug or Defect Cycle. As a manual Tester, we have to have this concept clear and well informed.

Thanks for watching ! 🙂 If you enjoyed it, hit that heart button below. Would mean a lot to me and it helps other people see the story.

798 total views, 12 views today


Automation Testing with — Stable & Fast Tests

In this is a tutorial, we are going to learn about how to setup and we will create some of the test cases and run and schedule it.

Feature in

  • Creating a Test
  • Recording and Playing back a test
  •  Labeling tests
  •  Validations and Assertions
  •  Screenshots
  •  Feedback on Each Step
  •  User Documentation
  • Grouping Parameterization
  • Version Control Branching
  • Reporting of Suite and Test Runs

Thanks for watching ! 🙂 If you enjoyed it, hit that heart button below. Would mean a lot to me and it helps other people see the story.

537 total views, 9 views today


Black Box Testing – Equivalent Class Partitioning Explained

It is used to minimize the number of possible test cases to an optimum level while maintains reasonable.

774 total views, 18 views today


Black Box Testing – Boundary Value Analysis Explained

In this tutorial, we are going to learn What is black box testing and How an efficient tester uses the Boundary value analysis.

441 total views, no views today


API Testing Tutorial with Frisby.js

In this tutorial, We are going to learn about how to Test REST API with a very fast, quick Javascript library, Frisby.js.

Thanks for reading! 🙂 If you enjoyed it, hit that share button below. Would mean a lot to me and it helps other people see the story.

837 total views, no views today


Impact of the GDPR on Software Testing

As you all know that the General Data Protection Regulation (GDPR) is coming in Few days and We can’t ignore it.


General Data Protection Regulation (GDPR) is one regulation that any development teams can’t ignore. We have to be compliant with these regulations.

If you are collecting user information, any personal Information like name, email, phone and other in your databases and putting them in your staging environment for Testing purpose or Production like Test data. You need to read below point to save it for GDPR. It would be better to remove or delete/mask it completely.

What is GDPR?
The General Data Protection Regulation regulates how companies protect EU residents’ personal data. It goes into effect on May 25, 2018. For every breach after that point, companies could incur fines of up to 4 percent of the company’s annual global turnover or €20 million (whichever is greater). Wow.

How to stay away from GDPR, Testers point of view?

  • Don’t Use Production’s Copy of Test-data if it includes some Sensitive or personal information.
  • Use Mocked or Dummy data sometimes we can them synthetically generate the test data while Testing in Staging.
  • If you have used the Production’s data in Staging and it is breached make sure you convey to respective authority.
  • You can use extract and mask technique, which basically has Production like a database but full masked and does not make any sense in real life.

So In a nutshell, Make sure as a tester in your Testing Procedure is compliant too to GDPR along with your Company.

Thanks for reading!
If you enjoyed it, hit that share button below. Would mean a lot to me and it helps other people see the story.

1,659 total views, 3 views today