Testing Output tool

8 messages Options
Embed this post
Permalink
Peter Gummer-2

Testing Output tool

Reply Threaded More More options
Print post
Permalink
What does the Testing Output tool do? I can't find any documentation for it.

    View | Tools | Testing Output

It just sits there and does nothing. Even if I put a print statement
into one of my tests and run it, nothing happens in the tool.

- Peter Gummer

fivaarno

Re: Testing Output tool

Reply Threaded More More options
Print post
Permalink

Hi Peter

The Testing Output tool was introduced in 6.4 for displaying AutoTest log messages. The plan for 6.5 is to extend the tool to show information about test execution/debugging and other tasks like test extraction.

Note that output printed in a test case can be viewed in the testing tool through the "Results" tab after double clicking on some test (the same location you find the exception trace for failing tests).

Regards,
Arno


--- In [hidden email], Peter Gummer <p-gummer@...> wrote:

>
> What does the Testing Output tool do? I can't find any documentation for it.
>
>     View | Tools | Testing Output
>
> It just sits there and does nothing. Even if I put a print statement
> into one of my tests and run it, nothing happens in the tool.
>
> - Peter Gummer
>


Peter Gummer-2

Re: Re: Testing Output tool

Reply Threaded More More options
Print post
Permalink
Arno wrote:
> Note that output printed in a test case can be viewed in the testing tool through the "Results" tab after double clicking on some test (the same location you find the exception trace for failing tests).
>  

Thanks Arno. That's the main thing I was looking for.

Unfortunately I don't see any output when I do that. Do I have to
compile my project as a console application? This is a vision2 project
that I'm running the tests in. Could that be why I don't see any output?

- Peter Gummer

fivaarno

Re: Testing Output tool

Reply Threaded More More options
Print post
Permalink
>
> Unfortunately I don't see any output when I do that. Do I have to
> compile my project as a console application? This is a vision2 project
> that I'm running the tests in. Could that be why I don't see any output?

I just ran a vision2 test which produces some output and at least on my Ubuntu machine the output is shown. It is not compiled as a console application but that might be platform dependent. This is what the screenshot looks like after double clicking on the test "test_app":

http://dev.eiffel.com/Image:Screenshot.png

To see the output you have to click on "Click here to view". I will try the same tomorrow on Windows. One reason for not seeing any output is when it gets printed in a different thread than what the test routine was called. For that I do not have a solution yet since `io' is once per thread.

Peter Gummer-2

Re: Re: Testing Output tool

Reply Threaded More More options
Print post
Permalink
fivaarno wrote:
> I just ran a vision2 test which produces some output and at least on my Ubuntu machine the output is shown.

I'm running on Windows. What part of the screenshot is the part you
printed in your test? Maybe the word "output"?

When I run all of my tests, I don't see anything at all in the Results
panel. Should I? It's completely empty. I don't think I've ever seen
anything on the Results panel.

We're not using threads in our code. The "multithreaded" project setting
is False.

- Peter Gummer

fivaarno

Re: Testing Output tool

Reply Threaded More More options
Print post
Permalink

>
> I'm running on Windows. What part of the screenshot is the part you
> printed in your test? Maybe the word "output"?
>

The actual output will be shown in a new window after clicking "Click here to view". The screenshot was meant to show how to get to the output.

> When I run all of my tests, I don't see anything at all in the Results
> panel. Should I? It's completely empty. I don't think I've ever seen
> anything on the Results panel.

The Results panel will not show anything until you double click on a specific test in the above class view (in the screenshot example I double clicked on the "test_app" row).

I understand that the current UI is not perfect, especially having to double click in order to see result details. As mentioned before I plan to redo some of this in 6.5. If you have suggestions please let me know (ideally by submitting a feature request on support.eiffel.com).


Peter Gummer-2

Re: Re: Testing Output tool

Reply Threaded More More options
Print post
Permalink
fivaarno wrote:
> The actual output will be shown in a new window after clicking "Click here to view". The screenshot was meant to show how to get to the output.
>  

But the Results pane is completely empty. There is nothing saying "Click
here to view".

> The Results panel will not show anything until you double click on a specific test in the above class view (in the screenshot example I double clicked on the "test_app" row).
>  

Yes, I know, you told me that before so I had done that. The Results
panel is always empty.

- Peter Gummer

Peter Gummer-2

Re: Re: Testing Output tool

Reply Threaded More More options
Print post
Permalink
I wrote:
>> The Results panel will not show anything until you double click on a specific test in the above class view (in the screenshot example I double clicked on the "test_app" row).  
>>    
>
> Yes, I know, you told me that before so I had done that. The Results
> panel is always empty.
>  

Hold on, now I see what you mean. I have to double-click on the test in
the panel at the top. I was clicking on the test in the Execution tab.
And if I add print ("hello") to my test, I get the "Click here to view"
link that you described. And when I click it a window opens saying, "hello".

Ok then, it is all working then. Thanks :-)

- Peter Gummer