request concerning unittest in the GUI
Saturday, 24 October 2015 · 6 messages · last reply 2 Nov 2015
RS
Rob Stapper24 Oct 2015 12:24 #
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
---
Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware. https://www.avast.com/antivirus
CG
Christian Grün28 Oct 2015 08:57 #
Hi Rob,
Makes sense; it's something that I would like to have as well. It's tricky to pass on the unit output to the GUI, but I've added a GitHub issue, and I will see what can be done [1].
Best,
Christian
[1] https://github.com/BaseXdb/basex/issues/1209
Quoted text · Rob Stapper · 28 lines
> 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 > > > > > > > > ________________________________ > > Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware. > www.avast.com > >
CG
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
Quoted text · Rob Stapper · 36 lines
On Sat, Oct 24, 2015 at 12:24 PM, Rob Stapper <r.stapper at 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 > > > > > > > ------------------------------ > [image: Avast logo] <https://www.avast.com/antivirus> > > Dit e-mailbericht is gecontroleerd op virussen met Avast > antivirussoftware. > www.avast.com <https://www.avast.com/antivirus> > >
RS
Rob Stapper31 Oct 2015 10:14 #
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
Quoted text · Christian Grün · 23 lines
Van: Christian Grün [mailto:christian.gruen at 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 at 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
CG
Christian Grün2 Nov 2015 13:05 #
Quoted text · Rob Stapper · 1 line
> - 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.
It has been like that before. The TEST command is the only one in the GUI that produces a textual result, even if an error occurs. I have slightly updated the code, it's available as usual via the latest snapshot.
RS
Rob Stapper2 Nov 2015 13:46 #
Works great, thanx.
Rob
-----Oorspronkelijk bericht-----
Quoted text · Christian Grün · 10 lines
Van: Christian Grün [mailto:christian.gruen at gmail.com] Verzonden: maandag 2 november 2015 13:05 Aan: Rob Stapper CC: BaseX Onderwerp: Re: [basex-talk] request concerning unittest in the GUI > - 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. It has been like that before. The TEST command is the only one in the GUI that produces a textual result, even if an error occurs. I have slightly updated the code, it's available as usual via the latest snapshot. --- Dit e-mailbericht is gecontroleerd op virussen met Avast antivirussoftware. https://www.avast.com/antivirus
Written for BaseX 8.3. BaseX may have changed since: please check the current documentation.
⚡Generated with XQuery