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
There's this idea of printing out progress to the user if a signal is sent to the running process (eg. with Ctrl+T on macOS or with kill -USR1 $PID on Linux)
For long-running elm-test instances, it might be nice to be able to get some progress info (eg. which tests are still running, how many fuzz iterations are left for each, how many failures has it already found, ...) mid-run.
The text was updated successfully, but these errors were encountered:
imo this would be a pretty obscure UI for most users. The goal seems to be giving interactive users a way to know what's happening when a test run is long. For that goal, imo the alternative #169 would be better.
There's this idea of printing out progress to the user if a signal is sent to the running process (eg. with
Ctrl+T
on macOS or withkill -USR1 $PID
on Linux)For long-running elm-test instances, it might be nice to be able to get some progress info (eg. which tests are still running, how many fuzz iterations are left for each, how many failures has it already found, ...) mid-run.
The text was updated successfully, but these errors were encountered: