You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As @Its-treason mentioned that currently the only option to debug scripts is to insert console.log() to print out some variables. May be that this approach is sufficient when creating new scripts.
I import a huge Postman collection into Bruno. After removing the syntax errors I am often "lost in space" because I can not see where to insert the console.log() statements to quickly see what is going wrong.
Therefore I hope to get some sort of support for debugging a script.
In the Mockup sections I provided a first idea of getting the checkbox for all scripts: collection, folder and request - all points in time: pre request, post response and tests.
If the check box is active the debugger should stop at the first line of the corresponding script. Furthermore the source of the script should be displayed in the chrome debugger tools.
As alternative to the check boxes you can provide a function called bru.breakpoint() (or similar) so the developer can write this into the source of a script to get the debugger stop at this line. I can not estimate which solution will need more effort.
Kind Regards,
Thomas
Mockups or Images of the feature
Here I show the UI implementation I wish:
The text was updated successfully, but these errors were encountered:
I have checked the following:
Describe the feature you want to add
Hi,
In #2319 I asked how to debug scripts and tests.
As @Its-treason mentioned that currently the only option to debug scripts is to insert console.log() to print out some variables. May be that this approach is sufficient when creating new scripts.
I import a huge Postman collection into Bruno. After removing the syntax errors I am often "lost in space" because I can not see where to insert the console.log() statements to quickly see what is going wrong.
Therefore I hope to get some sort of support for debugging a script.
In the Mockup sections I provided a first idea of getting the checkbox for all scripts: collection, folder and request - all points in time: pre request, post response and tests.
If the check box is active the debugger should stop at the first line of the corresponding script. Furthermore the source of the script should be displayed in the chrome debugger tools.
As alternative to the check boxes you can provide a function called bru.breakpoint() (or similar) so the developer can write this into the source of a script to get the debugger stop at this line. I can not estimate which solution will need more effort.
Kind Regards,
Thomas
Mockups or Images of the feature
Here I show the UI implementation I wish:
The text was updated successfully, but these errors were encountered: