June 4, 2018 by Promode on Testing

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.

1,038 total views, 3 views today

March 30, 2018 by Promode on Testing

Efficient TestCase for QA With Testing Template

Why need Testcases ?

Test case is a set of conditions under which a tester will determine whether an application or software system or one of its features is working as expected.’

Let’s discuss About the – TestCases

If the test cases are ready, they are really helpful to measure weather client expectations were fulfilled or not.

Demo
Website – https://tpromode.github.io/qa/
Temaplet at : https://goo.gl/SRSjFy

1,361 total views, 3 views today

February 2, 2017 by Promode on API Testing, Testing, Uncategorized

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.

January 24, 2017 by Promode on Testing

How to test Cron Job(Cron job testing)

What is Cron Job ?

The software utility Cron is a time-based job scheduler in Unix-like computer operating systems. People who set up and maintain software environments use cron to schedule jobs (commands or shell scripts) to run periodically at fixed times, dates, or intervals.

Below are the few points/Pre-made Test cases for the Cron Job Testing:-

Verify if It is scheduled correctly – By going here http://corntab.com/.
Mock the Cron time by 1-2 minutes by changing it for quick testing (if it’s long for hour/day long). – High
Ask the devs to create a shortcut for it. In the server or any other way to directly run it by you so that you can test it when you need.(saves time)
Ask dev to add the logs for monitor purpose and monitor it while testing.
Use below command for logs.
* * * * * /path/script.sh &> /path/script.log or
tail -f /var/log/cron
Do testing by doing changing things like we do in CRUD(Not always, Crud means update/delete etc whichever is relevant) and verify results. – High
Break something the job relies on upon and schedule it to run again in a few minutes – Verify the results.
After deployment – Validate it with real data also. – High
Keep system time and user system time in mind while testing CRON’s as scheduling is by server GMT time usually.
Negative scenario: What if CRON is stopped the midway execution, any impacts it will have?
Negative – Discuss with dev if there is any possibility of the same Cron getting run multiple times.
Negative – Discuss with dev if its fails to the job – What is the risk/ solution for it(did we get the mail if it fails ?)
Test for scenarios which shouldn’t get affected by Cron job(e.g. a other Cron should not affect other cron)

This is sample Cron job template in crontab

0/1 * * * * /usr/bin/python /home/my_username/hello.py > /home/my_username/log.txt

1	0/1 * * * * /usr/bin/python /home/my_username/hello.py > /home/my_username/log.txt

Hello.py:

<span class="com">#!/usr/bin/python</span>
<span class="com"># Hello world python program</span>
<span class="kwd">print</span> <span class="str">"Hello World!"</span>

#!/usr/bin/python

# Hello world python program

print "Hello World!"

January 21, 2017 by Promode on API Testing, Testing

API Testing using POSTMAN – Advance Test Cases

In this tutorial, We are going to write some TESTCASES in the POSTMAN Chrome as a part of API Testing.

API Testing includes

1. JSON Schema Validation
2. Response Time Verification
3. Verification of the Keys defined in response by API
4. Values as Expected (Data driven Testing) in response

Learn about JSON Schema – http://jsonschema.net

Code –
URL – https://jsonplaceholder.typicode.com/posts/1

Test Code –

tests["Content-Type is present"] = postman.getResponseHeader("Content-Type");
tests["Response time is less than 200ms"] = responseTime < 500;
tests["User ID is Present"] = responseBody.has("userId");
tests["ID is Present"] = responseBody.has("id");
tests["Title is Present"] = responseBody.has("title");
tests["API Bodyis Present"] = responseBody.has("body");

var jsonData = JSON.parse(responseBody);
tests["User ID should be "+jsonData.userId] = jsonData.userId === 1;
console.log("User ID I am getting from API is "+jsonData.userId);

var schema = {
"$schema": "http://json-schema.org/draft-04/schema#",
"type": "object",
"properties": {
"userId": {
"type": "integer"
},
"id": {
"type": "integer"
},
"title": {
"type": "string"
},
"body": {
"type": "string"
}
},
"required": [
"userId",
"id",
"title",
"body"
]
};


tests["Valid scehma"] = tv4.validate(jsonData, schema);

console.log("Validation failed: ", tv4.error);

tests["Content-Type is present"] = postman.getResponseHeader("Content-Type");

tests["Response time is less than 200ms"] = responseTime < 500;

tests["User ID is Present"] = responseBody.has("userId");

tests["ID is Present"] = responseBody.has("id");

tests["Title is Present"] = responseBody.has("title");

tests["API Bodyis Present"] = responseBody.has("body");

var jsonData = JSON.parse(responseBody);

tests["User ID should be "+jsonData.userId] = jsonData.userId === 1;

console.log("User ID I am getting from API is "+jsonData.userId);

var schema = {

"$schema": "http://json-schema.org/draft-04/schema#",

"type": "object",

"properties": {

"userId": {

"type": "integer"

"id": {

"type": "integer"

"title": {

"type": "string"

"body": {

"type": "string"

}

"required": [

"userId",

"id",

"title",

"body"

]

};

tests["Valid scehma"] = tv4.validate(jsonData, schema);

console.log("Validation failed: ", tv4.error);

January 14, 2017 by Promode on Selenium, Testing

Testing Techniques -Pairwise Testing using Pairwiser Tool

Today I am going to discuss Testing Techniques- Pairwise Testing. “Generate less number of combination with more test coverage.

What is Pairwise Technique?

A black-box test design technique in which test cases are designed to execute all possible discrete combinations of each pair of input parameters
Pairwise testing technique can dramatically reduce the number of combinations to be covered but remains very effective in terms of fault detection

Now let’s learn how to apply Pairwise Testing by this example.

Let’s take an example –
Suppose, we have a web app with one page that we have to do the Cross browser testing (CBT) e.g for IE, Chrome, Firefox, Opera, Safari and Cross OS testing with Windows, Mac, Ubuntu. We have another parameter like HTTP 1, HTTP 2 and resolution HD, NonHD(low resolution).

So Normal combination – 5*3*2*2 = 60
To perform 60 Test cases we will need about 180 minutes(assuming 3 minutes per Test Case).