So its some times bit difficult / time consuming for me to identify where exactly in the script/function the isssue is happening in order to fix them or take action. I.e it do not give a stack trace kind of information It do not give idea on where exactly the issue had happened Looking at the console will only give some idea about what is the issue (The issue could be something like, I have a empty response, and in the common function if I try to parse it to JSON format, it will give JSON exception, I could have handled it any way at the functiona definition level, but thats not the issue am trying to say here)Īnd in such situations the Postman will give notification that " Something went wrong while running your scripts. Now sometimes those functions will not work as expected because the passed argument could be of empty or something. And the functions that I invoke are called with these response arguments. I do come across some issues with the api endpoints sometimes due to various reasons that it do not return a response content or in other words give a empty body etc. I tried to make this pre-request scripts in such a way that, I write it only once at Collection or Folder level, then I re-use/invoke the same js functions at Tests tab of individual request endpoints present in the Collection. I do have some testing functions written at pre-request scripts tab of the Collection or at a particular folder level. I often run them either using postman Runner fetaure, or with Newman cmd tool
I do have a collection which is relatively a larger one with many requests and many Tests Is your feature request related to a problem? Please describe.
0 kommentar(er)
