So one MAJOR annoyance of the test suite collection execution method is that if I execute in parallel to gain execution efficiency then all the outputs from the scripts running in parallel are output to the same log, making things a jumbled mess to try to read what was occuring with what script when an error occurred.
Is there any way to force each suite in a collection to run in a separate log file and / or programmatically execute test suites in parallel such that they would have their own log file (essentially programmatically re-creating the test collection)?
So I usually have tree view turned off so that I can track each individual execution as it runs, and be able to jump back and forth between executions, with the Error messages highlighted.
In this view I can only see ONE script running, and ONE Job Progress item.
If I switch to Tree View; however, I can see where each of the scripts is running in parallel, however I can only track failed steps. As a result I tend to stay in non-Tree view all the time, and completely forgot about Tree view.
Will need to personally adjust to using Tree view during Collection runs
Interesting observations, I have notices similar behaviors in other toolsets due to CPU being taken up by reporting all the logging, really appreciate the methods shown above for getting rid of that tab!
Is there a way to bring the tab back for post-run investigations other than restarting Katalon entirely?
