Understanding Agile Testing

In this tutorial, We are going to cover what is Agile ? and What are its 12 Principles, Explaining agile to the newbies,

AGILE Consist of the four major rules : –

– Individuals and interactions over processes and tools:
– Customer collaboration over contract negotiation
– Responding to change over following a plan
– Working software over comprehensive documentation

Each one is discussed with example and explained how it important in software testing.

1,962 total views, 18 views today


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 machines.eg 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 — https://goo.gl/Fsq6fu : – 

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 – https://goo.gl/qjifHq
Instructions – https://goo.gl/gzhg1m
Grid Yaml – https://goo.gl/Fsq6fu


1,497 total views, 9 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’ – https://github.com/Evilweed/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 – https://github.com/Evilweed/protractor-beautiful-reporter

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.

3,059 total views, 33 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.

3,156 total views, no views today


API Testing using POSTMAN – Newman Basics

Newman – In simple words – Run postman collection commandline and exports results in different formats(html,json,xml etc) and number of times.

It’s created to keep CI in mind( Continous integration).
Build on node js.
Make sure(Node is installed).
Available for the Linux, windows and Mac

In this tutorial, we are building API test suite in Postman and Running it Command Line(Newman).


API Testing – Running Postman collection in the Docker

Most of the time people have the issue with installing software and dependencies. For example, we want to

Schedule the collection of the postman that we have created earlier using ‘POSTMAN’ tool, Rather than installing ‘newman’ command line tool, We will use a Docker image of Linux box with already installed ‘newman’.

I have been asked why I am getting the error, ‘newman’ not working etc, my os/system is having an issue while installing or running. This post definitely help you guys.

Understanding docker

Docker allows you to package an application with all of its dependencies into a standardized unit for software development.

In simple sentence consider it as a virtual machine which has ubuntu running with ‘newman‘ installed already.

Installing docker.

Navigate to the https://www.docker.com/products/overview#/install_the_platform. And Install it.
When you run it this is how it look like in Mac.






Pulling the docker images(Make sure you have the Docker install and started it)

  • docker pull postman/newman_ubuntu1404

Running postman collection using docker Command-line.

  •  docker run t postman/newman_ubuntu1404 url=“https://www.getpostman.com/collections/8a0c9bc08f062d12dcda”

Getting results.