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
We have unit tests which ensure errors are thrown. This means in the test output there will be a stacktrace. Normally this is fine, but since we're using property based tests, the tests run a large number of times. So large that it usually overflows console scrollback and even github's action logs won't display the entire logs.
To reduce this output we could simply hide all of it. However, it might hide problems and make troubleshooting a little more difficult. I think ideally we could do something like show the first stacktrace and then just a count of all the other ones. Perhaps the property based testing framework we're using even has something built in for this?
The text was updated successfully, but these errors were encountered:
We have unit tests which ensure errors are thrown. This means in the test output there will be a stacktrace. Normally this is fine, but since we're using property based tests, the tests run a large number of times. So large that it usually overflows console scrollback and even github's action logs won't display the entire logs.
To reduce this output we could simply hide all of it. However, it might hide problems and make troubleshooting a little more difficult. I think ideally we could do something like show the first stacktrace and then just a count of all the other ones. Perhaps the property based testing framework we're using even has something built in for this?
The text was updated successfully, but these errors were encountered: