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
{{ message }}
This repository was archived by the owner on Jul 29, 2024. It is now read-only.
When using multiCapabilities, the protractor process gets forked and the output of the subprocesses is buffered. The buffer is flushed to terminal only after an error or after the task finishes.
I didn't really like this, as I wanted to monitor the test execution in my test automation in real time, so I hacked my protractor to flush buffers immediately after every output.
Would you consider it a good idea to make something like this into a proper, configurable feature of protractor?
Best regards,
Jan
The text was updated successfully, but these errors were encountered:
Could you please update your issue to follow the format of the issue template? Also, if you could add more description of how you'd like feature to function (input/output examples would be great). Thanks!
Hi,
When using multiCapabilities, the protractor process gets forked and the output of the subprocesses is buffered. The buffer is flushed to terminal only after an error or after the task finishes.
I didn't really like this, as I wanted to monitor the test execution in my test automation in real time, so I hacked my protractor to flush buffers immediately after every output.
Would you consider it a good idea to make something like this into a proper, configurable feature of protractor?
Best regards,
Jan
The text was updated successfully, but these errors were encountered: