Visualize the export of test Results in Postman

 We use Postman to test various APIs. To ease our lives, we create collections and save those collections along with various test cases which further can be integrated with DevOps or automation testing frameworks. Let us assume, we did some changes in API and that API should be backward compatible. In such cases, these collections can be used to test the old functionality is not broken. The results output from testing plays an important role in Software Development Lifecycle(SDLC). While using the Postman GUI, we can run the collections and it will give the response in the GUI layout.

After selecting a collection to run, it will give various parameters to select. We can select as per our need. Once we click on Run <Collection Name>(Run Postman Echo)

Once we run the Postman Collection, it will give us the output in a beautiful GUI layout. Now to save results, we have only one option i.e. to Export Results as highlighted in the above image.


Once, we click on Export Results, it gives us output in the form of JSON. This JSON output sometimes feels a bit tricky to visualize. What if we need to see in GUI after some time and we have only this JSON export.

To do so, we can make use of Postman Echo API and Visualizer.

Postman Echo API can be used to echo our JSON test results export and pm.visualizer.set() function under the test tab of the Postman request can be used to populate the echoed data in HTML tags and visualize it.

For this, we have created a sample request in the public collection under Postman Public workspace.

Steps to use

1. Click on Run in Postman Button

2. Fork or import the collection to your Postman workspace.

3.  Open the request "visualize test results json"

4. Paste the exported results.JSON file data in the request body.

5. Click on Send, to trigger the request to Postman echo API.


We can see JSON data formatted in the form of an HTML Document under Visualize Tab.

Resources:

  1. Sample JSON test results export data
  2. Postman Public Workspace
  3. Postman Echo API
  4. Visualizer documentation
If you have any suggestions, feel free to comment or raise a pull request on Postman Public Workspace. Please share your valuable feedback 
😊😊😊



-

Comments

Post a Comment

Popular posts from this blog

DateTime formatting using xp20:format-dateTime ()

xs:dateTime Format In XML, we generally use xs:dateTime(xs:xmlns="http://www.w3.org/2001/XMLSchema") data type to store date time data. The generic representation of date time, that is supported by xs:dateTime in xml: YYYY-MM-DDThh:mm:ss[.SSS][Z|(+|-)hh:mm] Example :  2019-09-11T10:16:31.943+05:30 Code Description Example YYYY represents a 4-digit year 2019 MM represents a 2-digit month 09 DD represents 2-digit date 11 hh represents 2-digit hours 10 mm represents minutes in 2-digits 16 ss represents seconds in 2-digits 31 SSS represents milliseconds 943 T represents time separator T Z represents UTC time zone or 0 time zone offset (+|-)hh:mm represents time zone offset +5:30 Few more valid examples : 2019-09-11T21:32:52, 2019-09-11T21:32:52+02:...
Read more

Create Delimited String from XML Nodes and Vice Versa in SOA 12c

A delimited string is a string representation of data separated by a delimiter(e.g. ","). A simple representation of the delimited string will look like. Delimited String Examples Sample-1-- Delimiter as ","        Value1,Value2,Value3   Sample-2-- Delimiter as "|"        Value1|Value2|Value3 If we want to represent the above set of delimited values in the form of an XML document under some root and parent tag. The representation will look like this. XML Example <root xmlns="http://test.com/sample/xml">   <Values>     <value>Value1</value>     <value>Value2</value>     <value>Value3</value>   </Values> </root> Sometimes we may need to convert values coming in delimited string to an xml document or vice versa. Since delimited strin...
Read more

Import and Export MDS artifacts in SOA 12c

Image
Oracle SOA-MDS (Metadata Store) repository can be used to access artifacts that can be shared among various SOA composites. For example, we have one common schema for a business fault that is consumed by various applications. Instead of having a localized copy of that schema file in each SOA composite, we can have it in a centralized repository (SOA-MDS). Another benefit of using SOA-MDS is that we can change the file at runtime and need not redeploy the complete code. While developing SOA composites, we use SOA design-time repository, later these changes can be synced to the SOA servers. In this article, we will discuss 2 ways to sync the artifacts available in the SOA design-time repository and the SOA servers. Establishing the connection to SOA-MDS in Jdeveloper. Using SOA em console or Fusion Middleware control console. Moving a file between SOA composite to SOA design-time MDS repository Let's assume, we created a businessFault.xsd which wi...
Read more