Hi Christian, One small remark, and I don’t know if it is changed behavior or that it already existed in the previous versions: - In case of an unit-test-error the GUI only shows the “Query-info”-window and not automaticly the “Result”-window with the unit-test-error-details (anymore?). I would guess that, certainly in case of unit-test-errors, the result-window with error-details would automaticly appear. Best, Rob Van: Christian Grün [mailto:christian.gruen@gmail.com] Verzonden: vrijdag 30 oktober 2015 15:56 Aan: Rob Stapper CC: BaseX Onderwerp: Re: [basex-talk] request concerning unittest in the GUI Hi Rob, Thanks for your testing feedback. @Everyone: The GUI Info View panel now includes trace output, even if XQUnit errors are failing. Best, Christian On Sat, Oct 24, 2015 at 12:24 PM, Rob Stapper <r.stapper@lijbrandt.nl> wrote: Hi Christian, For debugging my xquery-code I using the test-facilities from the unit-module in combination with trace and prof:dump command in the code for code-tracing. The problem is that when a unit-test fails it overwrites the trace-output in the Query-info window. So the code-tracing-info is gone just when I need it. It would make debugging a lot easier if the trace-output is appended after the unit-test-output in the Info-window of the GUI. Best, Rob _____ <https://www.avast.com/antivirus> Afbeelding verwijderd door afzender. Avast logo Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware. www.avast.com <https://www.avast.com/antivirus> --- Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware. https://www.avast.com/antivirus
