Postman Console is specially designed to aid debugging Postman collections and API calls.Network calls from NodeJS does not show up inside Electron’s console. We recently moved to NodeJS driven runtime.That gets mixed with console logs from user scripts, making it difficult to distinguish between the two. The original console is usually a place where Postman logs its internal debugging entries.The internal JavaScript console of electron (using which Postman is built with) is available for use, then why make a separate console? If you know your way around console.log in Javascript, this is exactly the same. More details on how I do it is a discussion for the future. But not any more, as I can now put or console.warn at appropriate locations in my scripts and extract the exact line of code that is acting up. And when I manage to mess them up, debugging it becomes even more complicated. The backstory on this is very simple – I have test scripts in Postman Collections that do some really complicated stuff. The last item ( console.log output) is the another compelling reason why I keep going back to Postman Console. Error logs from test or pre-request scripts.What proxy and certificates were used during making the request.The exact response sent by the server before it is processed by Postman. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |