April Is API Month

April is marked as "API Month" officially by POSTMAN. Do check out the post in the below link...

Click Me

API Testing 'A Beginners View': Everything about ‘Postman Student Expert Program’

Hey Guys!!! Greetings For The Day!!!

Postman Student Expert Program is designed to help students get trained on APIs and educate their peers. Postman Student Experts are proficient in the essential skills involved in building and testing API requests in Postman.

As a Postman Student Expert, you will receive API and Postman training created by the Postman team. Postman Student Expert Badge to showcase online and future employers. Exclusive access to Postman meetups and events like Postman Galaxy, the Postman user conference.

Do check out more information on Postman Student Expert Program here

To enroll yourself in the program Click Here

My Personal Experience on Postman Student Expert Program: This program is a great initiative of the POSTMAN team, I really enjoyed the entire training and assessment process, it's self-paced easy to follow, and get through the module. Every single request is interesting. On completion of my training and assessment, I received my Open Badge ‘Postman Student Expert’ Badge. You can share the Open Badge all over the web, including posting it to your social media feeds and adding it to your LinkedIn profile as certification so that potential employers and connections see it! I did mine.

So here you can view my Postman Student Expert Badge.

Happy to share this useful article!

Have a great day! 😇

API Testing 'A Beginners View': Data-Driven Testing In Postman

Hi Everyone!!! Let's check out some details about Data-Driven Testing with Postman using CSV and JSON files😊

Data-driven testing can be a very effective approach in testing an API against different data-sets. Postman supports CSV and JSON files to get data for the test scripts. The data-driven approach is useful when we need to execute a test with multiple sets of Data. Also, modifying or adding any data fields will just need updating the data files which is easier than going to test script and updating test data. 

To explain the same I’ll use a sample request which I use in my daily work.

Steps to do this:-

1. Now, in this example, I want to refer Row_No, UCI_Number, and Entity_ID from a CSV file. So, as a pre-requisite, we need to define these in a variable. In order to do so in the Pre-request Script tab we need to set the variables as in the screenshot, so that going ahead values will be read from variables.
2. Create a CSV file having these variables and values.
3. Now go to Collection Runner, and import this data file and click on the Run button. Data File Preview:

After hitting on the run:

Run can be stopped any time of execution:

API Testing 'A Beginners View': Newman API Testing

Hi Everyone!!! Let's check out some details about NEWMAN 😊

Newman gives the capability of running Postman collections through the command line. It basically helps you automate your Postman tests with ease.

Got some insight on this from my daily worklife. So why wait Let's get started! 

Basic Steps of NEWMAN Kickstart:

1. Step 1: Install NodeJS
2. Step 2: Install Postman's Newman
3. Step3: Create a Collection and Running Tests Scripts
4. Step4: Exporting Postman Collection and its associated Environment file if applicable
5. Step5: Running the Collection in Newman

Step1: Install NodeJS

Installing NodeJS is pretty straight forward, visit their download page here, download your platform version to install.

Note: Kindly make sure to install the latest higher version.

After installing, go to your Terminal and enter the command below to check if everything is fine to go.

• node -v 
• npm -v

You should see an output similar to the one below:

 

Step2: Install Postman's Newman :

Now that NodeJS is set up, we need to install "Newman" and some NodeJS modules that will be useful for our test report generations.

Run the below command:

• npm install newman request rimraf newman-reporter-html newman-reporter-htmlextra --save --force

After installation you will see similar output:

Step3: Create a Collection and Running Tests Scripts

In Postman select "New" >> "Collection". Give a name to the collection. I’ll be using a sample collection in my local which has Test Scripts designed already just for the purpose of the explanation.

Sample Collection with Test Scripts:

 

Step4: Exporting Postman Collection and its associated Environment file if applicable

Under the ‘View more actions' option of the collection, select ‘Export’.

Save the Collection to your local directory. The collection should be saved as a .postman_collection json file.

Note: To export the environment variables, Go to the ‘Manage Environment’ section from the top right corner and click on Download, environment file will be downloaded as .postman_environment json file

Step5: Running the Collection in Newman

Open the terminal and navigate to where the Postman Collection and associated environment json file is saved. To execute the tests run the below command:

newman run Jenkins-Testing.postman_collection.json -e Reltio-MDM-UCI.postman_environment.json --export-environment Reltio-MDM-UCI.postman_environment.json

Similar output will be prompted:

Collection executed successfully through the command line.

Now somebody might think why did I pass the environment file twice in a different way. Let me explain it why? 

The Collection that I used above for my explanation needs an access token to be generated freshly for each run. Could we not just attach a token to the tests, export the collection and put them into our CI? No we can’t. That would work for a while but the tests would fail once the access token expires. So any access token I attach to my Postman collection to run in CI is eventually going to be invalid.

We need a way of automatically generating a fresh access token and passing it into our Postman tests. In CI terms, we need to be able to generate an access token on every run of tests. In order to achieve this, I have added an environment variable to store the access token that gets generated by a request of Authentication. So now when we send a request for an access token we can now grab that access token from the response and attach it to any future responses we need. But wait a min by POSTMAN the scenario will work fine but NEWMAN does not update the environment variables file during a run of tests. So to save the new values of the environment variables after a collection run, simply add this argument when running the collection that updates the variables: --export-environment OurEnvironmentFile

In our case :

newman run Jenkins-Testing.postman_collection.json -e Reltio-MDM-UCI.postman_environment.json --export-environment Reltio-MDM-UCI.postman_environment.json

That’s it and now we are familiar with the basics of NEWMAN.

Hope the article was useful! Happy Learning! 😊

API Testing 'A Beginners View': How to receive notification of POSTMAN Test execution completion in GOOGLE CHAT ROOM

Google chat API is an interesting API that lets you to get notification of the Test Scripts execution completion for every run. Just install GOOGLE CHAT in your machine and follow the below steps and that’s it

Steps to it:

1. Create a room in Google chat (Addin the member's list).

2. Room is setup:

3. Select “Manage webhooks” as displayed below:

4. Type any name as per your need and click save:

5. Copy the link to the Clipboard. Open your collection/folders, just add this as a new POST request to the existing ones.

6. Click on  “Send”:

In this BOT you can add some Test Scripts based on the previous requests execution status to showcase the Test Report.

Sample is below:

var resp = JSON.parse(responseBody);

console.log(resp);

  //Checking the Response Status Code

    pm.test("Response is Successful with Status Code 200", function () 

    {

    pm.response.to.have.status(200);

    console.log("Response is Successful with Status Code 200");

    });

// this counter is from previous step (in your script need to define it)

to check the completion of run

 const counter_check = pm.environment.get("counter");

 if(counter_check == 10) 

 {

     pm.test("Execution Passed" , function () 

        {

        console.log("Execution Passed");

        });

 }

 else 

    {

        pm.test("Execution Failed" , function () 

        {

        pm.expect.fail('Execution failed, please check test results of previous steps');

        });

    }

 

Happy Learning 😇

Hope this was useful 😇

Basic Collection for Beginner’s to kick start with POSTMAN - API Testing ‘A Beginners View’

Hello Friends!!!

Here is a simple collection for Beginners like me to kick start with POSTMAN 

Collection URL:

https://documenter.getpostman.com/view/12559118/Tz5p6xux

This collection contains:

• Basic test syntax

• Sample ‘Test Scripts’ to get started with POSTMAN

  Resources

  Do check the Blog for a detailed description of the requests

  • Blog: https://softwaretestingcafebyjency.blogspot.com/ 1

Happy Learning!!! 😇

API Testing 'A Beginners View': Environment and Variables In POSTMAN

In this post let’s try to have a better understanding of the Environment and Variables in POSTMAN

Let’s start with Variables: A variable is a bucket that holds values that can be changed. Suppose you are developing a mobile application. There are some values that will be used throughout the application or some values might be unique to a functionality. Hardcoding of values everywhere in the design is not a good practice in such situations variables can be used. Define a variable as per your need i.e. locally or globally and use its referenced name wherever needed. If you are required to update the value of a variable, just update the value where you have declared. Everywhere updated values will be used.

The same concept applies to Postman. We have many usages of variables in Postman. Let's check out a few of them:

1. In our day-to-day work life, we might need to test systems in different environments like QA, Dev, Stage, etc which would have a different set of domains. Here variables make our job easier. We can store the domain name as per environment in a variable and can call that variable here.
2. We can use variables at several places to make it parameterized such as Query- parameters, headers, authorization, request body.
3. Variables can be used to chain requests in the collection. Extracting data from response, storing, and using it for another request as input are possible by using variables.
4. Variables can also be used in Pre-request and Tests Scripts. 

Next, Let’s Understand Environment: Environment in POSTMAN is a set of variables that can be assigned a value and used during your work. The environment is tied to the current operating environment: each operating environment has its own POSTMAN environment. To visualize this, I have created an “API Testing 'A Beginners View'” environment with some variables.

There are two columns for the variable's value. The only difference is that if you share your environment with your team, then the value from the first column will be shared.

Let's check out some usage of Environments:

1. We can create, share, duplicate, export, and delete an environment. 
2. You can download it as JSON.
3. Variables defined in an Environment are Local variables. It means you cannot use variables of an environment in another environment. To solve this we have another type of variable called Global variables. Global variables do not belong to specific environments. It is available in all scopes. You can not select multiple environments at the same time. In that case, Global variables will be helpful.

API Testing 'A Beginners View': How to use JavaScript Arraylist in POSTMAN using counter? & How to reset the counter after run?

Q. 1 How to use JavaScript Arraylist in POSTMAN

Let assume that you have an array (or any collection) of items, each of which you need to pass into the request one by one. How do we do this? 

This was one of my major questions that were running through my mind these days after knowing how to store a list of response values as variables. On doing some R&D and checking with friends I got to know about the usage of counters and I was able to solve my problem. So today let’s check out how I tackled this.

You need to do the below things as a start in POSTMAN:

• Create a variable  (does not matter in Globals or Environment scope).
• Set Initial and current value = 0 (current value will incrementally increase.)

Now in the Request on «Pre-request Script» tab you need:

• Get the array of items from the variable that you prepared to hold the array of records.
• Get an index for current request from variable;
• Set an item according to an index into another variable for the current request.
• Increment index and save a new value after current request. It will be used for request a new item on the next iteration;

Example is below:

let value = pm.environment.get("countArr");

let item = pm.environment.get("itemOfArray");

pm.environment.set("ABC", value[item]);

pm.environment.set("itemOfArray", Number(item) + 1);

Now run your single request in Collection Runner. Before starting you need:

• Set a number of iterations = quantity of your itemOfArray;
• Iterations = array.length

Q.2 How to reset the counter after a run?

The next thing while working popped my mind was about the reset of the counter, why to manually reset it after every run, then on doing some googling work got an idea of creating a pre-request script in the previous request which pushes the response value to an array to reset the counter after the whatever static iterations we want the counter to be reset. In my case I wanted the counter to be reset after 10 iterations so used the Pre-Request script option and tried the below snippet:

//resetting back to 0 the counter

let count_array = pm.environment.get("itemOfArray");

console.log(count_array );

    if ((count_array  == 10)) 

    {

        pm.environment.set("itemOfArray","0");

        console.log(count_array);

    }

A simple way of resetting 😊 and it worked for me.