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
While developing tests it is quite handy to put in breakpoints or extra prints. At the moment, when a test is run by green, breakpoints do not work because stdin is not connected to the terminal. I couldn't find any option to preserve stdin. This means I have to switch to running the test without green. While not the end of the world, it's inconvenient. It would be great if green had a command-line option to support test debugging. It could do the following:
Leave stdin connected. Optionally complain if stdin is not a tty.
Don't capture stdout.
Limit the number of processes to 1.
I think that will make developing tests with green more pleasant.
The text was updated successfully, but these errors were encountered:
While developing tests it is quite handy to put in breakpoints or extra prints. At the moment, when a test is run by green, breakpoints do not work because stdin is not connected to the terminal. I couldn't find any option to preserve stdin. This means I have to switch to running the test without green. While not the end of the world, it's inconvenient. It would be great if green had a command-line option to support test debugging. It could do the following:
I think that will make developing tests with green more pleasant.
The text was updated successfully, but these errors were encountered: