Enabling Chrome Developer Tools inside Postman

Chrome's Developer Tools are an indispensable part of the modern web development workflow. However, accessing them inside the Postman packaged app takes a few steps. To enable them:

  1. Type chrome://flags inside your Chrome URL window
  2. Search for "packed" or try to find the "Enable debugging for packed apps" setting
  3. Enable the setting
  4. Restart Chrome

chrome___flags

You can access the Developer Tools window by right clicking anywhere inside Postman and selecting "inspect element". You can also go to chrome://inspect/#apps and then click "inspect" just below requester.html under the Postman heading.

Once enabled, you can use the Network Tools tab for even more information on your requests or the console while writing test scripts. If something goes wrong with your test scripts, it'll show up here.

Developer Tools inside Chrome are really powerful and now with the ability to write test scripts inside Postman, you can use them for debugging and logging. For more information on Chrome Developer Tools, check out these tutorials.

20 thoughts on “Enabling Chrome Developer Tools inside Postman”

      1. The blog requires and email address to view, no thank you, anyway Postman can do a blog post on how to log more info about the collection runner test results

  1. Seems like a good idea but can't get it to work. Specifically I can't open the context menu in Postman to inspect the DOM. I'm working on a Mac. Don't know if this is a general problem.

  2. I've come here to find a way to see tv4's validation errors when validating the JSON payload being returned. The above helped to see the errors in the console. I wanted to see them in the test results and managed to do so via

    var data = JSON.parse(responseBody);

    var result = tv4.validateResult(data, schema);

    var isValid = result.valid

    if (!isValid) {

    tests["Invalid Schema: " + result.error + " at " + result.error.dataPath + " (" + result.error.schemaPath + ")"] = isValid;

    }

    else {

    tests["Valid Schema"] = isValid;

    }

    to circumvent the limitation of outputting validation results.

    Might be useful to somebody passing by.

  3. How do you make this work for the other version of postman? How do you call that? The unpackaged version?

    I also tried this on the packaged version and I think I'm missing something here. I'm getting a "Defining mode" output instead of the expected output of "console.log('test')".

    What am I doing wrong?

  4. This does not show the original XHR request headers, it's only showing the contents of the response.html file and a GET request to it.

  5. postman can't sent any request

    extensions::platformApp:17 window.localStorage is not available in packaged apps. Use chrome.storage.local instead.(anonymous function) @ extensions::platformApp:17

    extensions::platformApp:17 beforeunload is not available in packaged apps.(anonymous function) @ extensions::platformApp:17

  6. I go to chrome://inspect/#apps and I don't see Postman there. Is is possible it's not really a Chrome app?

Leave a Reply

Your email address will not be published. Required fields are marked *