[326] Trace Output To OutputWindow

Is there a way to send output to the OutputWindow while using the R#
UnitTest runner? We are running acceptance tests that are defined in files
and would like to be able to press F8 to go to the failure and fix them in
the correct spot.

By the way, that would be better than the current way R# shows the places
where failures occur as (unless I missed a keyboard shortcut) to go to the
correct file location you need to use the mouse, while going using F8 /
Shift+F8 is much more faster...

Regards,
Pablo

--

We demand source because we've been burned too much by its lack, not
because
we have this desire to add custom hacks to our kernels or utilities.
Believe
me, we'd all like to run stock systems, straight off the vendor
distribution
tapes; it'd be significantly less work. But our users have this liking
for
working systems and prompt fixes for the bugs they find, neither of which
the
vendors we buy from have been particularly good in supplying.
-- cks@hawkwind.utcs.toronto.edu

Pablo Montilla
www.odyssey.com.uy

4 comments
Comment actions Permalink

Hello Pablo,

Ctrl-Alt-Up/Down are default shortcuts for navigating ReSharper's views.
Commands are called ReSharperAddIn25.GotoNextOccurence ReSharperAddIn25.GotoPreviousOccurence
in keyboard settings, if you wish to change shortcuts.

Hint: you may wish to browse ReSharper Tips (Resharper > Show Tips) to learn
more about ReSharper.

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


PM> Is there a way to send output to the OutputWindow while using the R#
PM> UnitTest runner? We are running acceptance tests that are defined in
PM> files and would like to be able to press F8 to go to the failure
PM> and fix them in the correct spot.
PM>
PM> By the way, that would be better than the current way R# shows the
PM> places where failures occur as (unless I missed a keyboard
PM> shortcut) to go to the correct file location you need to use the
PM> mouse, while going using F8 / Shift+F8 is much more faster...
PM>
PM> Regards,
PM> Pablo
PM> --
PM>
PM> We demand source because we've been burned too much by its lack, not
PM> because
PM> we have this desire to add custom hacks to our kernels or
PM> utilities.
PM> Believe
PM> me, we'd all like to run stock systems, straight off the vendor
PM> distribution
PM> tapes; it'd be significantly less work. But our users have this
PM> liking
PM> for
PM> working systems and prompt fixes for the bugs they find, neither
PM> of which
PM> the
PM> vendors we buy from have been particularly good in supplying.
PM> -- cks@hawkwind.utcs.toronto.edu
PM> Pablo Montilla
PM> www.odyssey.com.uy


0
Comment actions Permalink

What I meant (probably I wasn't completely clear) was to be able to use
the keyboard to go where the test has failed. With the UnitTestRunner as
it is, I need to reach the mouse, most of the time scroll, and then click
to go the the line where a test failed.

An example:
System.NotImplementedException: The method or operation is not implemented.

at O2.Data.SecurityPayment.get_Total() in SecurityPayment.cs:line 14
at
O2.Data.Services.SecuritiesServicePaymentsTest.DistributesPaymentEqually()
in SecuritiesServicePaymentsTest.cs:line 54

The part where it says 'SecurityPayment.cs:line 14' is nicely underlined
and I can click on it to go the the 14th line in the SecurityPayment.cs
file, but I can't (unless I've missed it) go to that line using the
keyboard.

I would also like it to be visible when my window is not big enough (by
putting it a the start of the line)...otherwise I need to scroll (as
messages are usually lengthier) to know where the error was.

I apologize if I didn't explain myself correctly...

Regards,
Pablo

On Tue, 09 Jan 2007 14:17:43 -0200, Ilya Ryzhenkov <orangy@netix.ru> wrote:

Hello Pablo,

>

Ctrl-Alt-Up/Down are default shortcuts for navigating ReSharper's views.
Commands are called ReSharperAddIn25.GotoNextOccurence
ReSharperAddIn25.GotoPreviousOccurence in keyboard settings, if you wish
to change shortcuts.

>

Hint: you may wish to browse ReSharper Tips (Resharper > Show Tips) to
learn more about ReSharper.

>

Sincerely,
Ilya Ryzhenkov

>

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>

PM> Is there a way to send output to the OutputWindow while using the R#
PM> UnitTest runner? We are running acceptance tests that are defined in
PM> files and would like to be able to press F8 to go to the failure
PM> and fix them in the correct spot.
PM> PM> By the way, that would be better than the current way R# shows
the
PM> places where failures occur as (unless I missed a keyboard
PM> shortcut) to go to the correct file location you need to use the
PM> mouse, while going using F8 / Shift+F8 is much more faster...
PM> PM> Regards,
PM> Pablo
PM> --
PM> PM> We demand source because we've been burned too much by its lack,
not
PM> because
PM> we have this desire to add custom hacks to our kernels or
PM> utilities.
PM> Believe
PM> me, we'd all like to run stock systems, straight off the vendor
PM> distribution
PM> tapes; it'd be significantly less work. But our users have this
PM> liking
PM> for
PM> working systems and prompt fixes for the bugs they find, neither
PM> of which
PM> the
PM> vendors we buy from have been particularly good in supplying.
PM> -- cks@hawkwind.utcs.toronto.edu
PM> Pablo Montilla
PM> www.odyssey.com.uy

>
>



--

--

As for the virtuous poor, one can pity them, of course, but one cannot
possibly admire them.
-- Oscar Wilde

Pablo Montilla
www.odyssey.com.uy

0
Comment actions Permalink

On Tue, 09 Jan 2007 14:17:43 -0200, Ilya Ryzhenkov <orangy@netix.ru> wrote:

PM> Is there a way to send output to the OutputWindow while using the R#
PM> UnitTest runner? We are running acceptance tests that are defined in
PM> files and would like to be able to press F8 to go to the failure
PM> and fix them in the correct spot.


What we have are acceptance tests that are defined in a simple mini
language that gets pages from our server, and checks its output using a
transformation. We use the directory structure and this files to generate
a cs test suite. It works great but I would like to be able to go to the
file that generates the errors.

I'll try to explain using an example:

We have a file named Acceptance.test with this lines:
Customer/List.aspx -> Customer/List.xml
number = 1

Customer/List.aspx -> Customer/List.printer
number = 1

We generate a fixture with a member:

[Test,Category("Customer")]
Acceptance()
{
runner.Execute("Acceptance.test");
}


Now, when we have a failure in Customer/List.printer, we now which line is
that's failing, but can't point to it in any way, unless we run this with
nunit-console, in which case outputing the
"$fullPath$Acceptance.test(#lineNumber): error TEST: " as suffix leaves us
an error that we can access by pressing F8.

I want to be able to do the same, but using the R# Test runner...

Hope I explained it better.

Thanks,
Pablo
--
As for the virtuous poor, one can pity them, of course, but one cannot
possibly admire them.
-- Oscar Wilde

Pablo Montilla
www.odyssey.com.uy

0
Comment actions Permalink

VS Output window is not supported :(

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Pablo Montilla" <melkor@odyssey.com.uy> wrote in message
news:op.tknv0fbtcj6shk@athena...

Is there a way to send output to the OutputWindow while using the R#
UnitTest runner? We are running acceptance tests that are defined in files
and would like to be able to press F8 to go to the failure and fix them in
the correct spot.

>

By the way, that would be better than the current way R# shows the places
where failures occur as (unless I missed a keyboard shortcut) to go to the
correct file location you need to use the mouse, while going using F8 /
Shift+F8 is much more faster...

>

Regards,
Pablo

>

--

>

We demand source because we've been burned too much by its lack, not
because
we have this desire to add custom hacks to our kernels or utilities.
Believe
me, we'd all like to run stock systems, straight off the vendor
distribution
tapes; it'd be significantly less work. But our users have this liking
for
working systems and prompt fixes for the bugs they find, neither of which
the
vendors we buy from have been particularly good in supplying.
-- cks@hawkwind.utcs.toronto.edu

>

Pablo Montilla
www.odyssey.com.uy



0

Please sign in to leave a comment.