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
Testing frameworks like Backbone, which do not litter the console with logs gives conscious and legible output - the summary first and then the list of failures, if there were any. However, when dealing with legacy code, which uses console.log, many "useless" log lines may follow the failure summary. It makes looking up the failures more difficult by scrolling up the console to find the failures.
How about introducing a new option like suppressBrowserLogs to suppress the log printing?
The text was updated successfully, but these errors were encountered:
Testing frameworks like Backbone, which do not litter the console with logs gives conscious and legible output - the summary first and then the list of failures, if there were any. However, when dealing with legacy code, which uses console.log, many "useless" log lines may follow the failure summary. It makes looking up the failures more difficult by scrolling up the console to find the failures.
How about introducing a new option like
suppressBrowserLogs
to suppress the log printing?The text was updated successfully, but these errors were encountered: