Hi,
When running tests from the GUI I sometimes insert debugging code to figure out which tests fails or why. The current behavior of the GUI makes this impossible though because when tests are run this info is printed to the Query Info window but immediately after tests are run it prints the test summary overwriting the debugging info (such as trace output).
Currently I then go to the command-line but it might be an idea to somehow keep the output generated during test run visible.
Cheers, --Marc
Hi Marc,
I perfectly agree… It's a bit tricky indeed to cache all the debugging information in the GUI mode, but we are frequently running into this, too. I'll see what I can do.
Best, Christian
On Sat, Mar 21, 2015 at 6:16 PM, Marc van Grootel marc.van.grootel@gmail.com wrote:
Hi,
When running tests from the GUI I sometimes insert debugging code to figure out which tests fails or why. The current behavior of the GUI makes this impossible though because when tests are run this info is printed to the Query Info window but immediately after tests are run it prints the test summary overwriting the debugging info (such as trace output).
Currently I then go to the command-line but it might be an idea to somehow keep the output generated during test run visible.
Cheers, --Marc
basex-talk@mailman.uni-konstanz.de