NUnit 2.6 RC - Issue with test time print out
Ryan Boggs
Just grabbed NUnit 2.6 release candidate. It seems to be working ok so far but the test result time print out seems to be inconsistent. Sometimes a time will print out fine while other times, it'll just display "Time: seconds". NUnit 2.5 doesn't seem to have this problem.
FYI - I am working on updating NAnt's nunit2 task with the latest version of nunit, which is where I am running into this issue. If anyone is interested, my repo is here:
https://github.com/rmboggs/nant/tree/nunitupdates
Thanks,
Ryan
Charlie Poole
Is this problem with the Gui or the console runner? If it's the Gui, there
are several places where the time is displayed, so please indicate which.
Have you found a particular way to trigger this problem?
Charlie
> --
> You received this message because you are subscribed to the Google Groups
> "NUnit-Discuss" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/nunit-discuss/-/T4XqPZtNX_wJ.
> To post to this group, send email to nunit-...@googlegroups.com.
> To unsubscribe from this group, send email to
> nunit-discus...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/nunit-discuss?hl=en.
Ryan Boggs
https://github.com/rmboggs/nant/blob/nunitupdates/src/NAnt.NUnit/NUnit2/NUnit2Task.cs
This issue seems to be happening to certain test dlls. Let me see if
I can get a log file together to help illustrate this issue further.
Thanks,
Ryan
Charlie Poole
From the code, it seems you are creating the output yourself, using the
xsl transform. Since NUnit no longer uses it, I suppose it's possible that
the XML format and the transform have diverged. Take a look at what's
in the raw xml file for the cases where you have incorrect output.
Charlie
Ryan Boggs
tests that are ignored. At least in the xml test results file. I'll
post the output xml files somewhere if needed. Please let me know.
Thanks,
Ryan
> xsl transform. Since NUnit no longer uses it, I suppose it's possible that
> the XML format and the transform have diverged. Take a look at what's
> in the raw xml file for the cases where you have incorrect output.
>
> Charlie
>
>
>
>
>
>
>
> On Mon, Feb 6, 2012 at 9:17 AM, Ryan Boggs <rmbo...@gmail.com> wrote:
> > I'm using the API directly. Code file can be found here:
Charlie Poole
have a time, since it didn't run. But that should not impact the summary unless
the assembly as a whole was ignored. Try running against mock-assembly.dll,
which has some ignored tests.
Charlie
Ryan Boggs
Just grabbed NUnit 2.6 release candidate. It seems to be working ok
so far but the test result time print out seems to be inconsistent.
Sometimes a time will print out while other times, it'll just display
Ryan Boggs
issue. Go ahead and ignore the email above.
I tested mock-assembly.dll and it printed out normally. Upon closer
inspection of my test lib xml results, nunit is marking my whole
assembly as "executed=false, result=ignored" even when just a small
handful of tests are ignored. The mock-assembly is being marked as
"executed=true, result=error".
<test-suite type="Assembly" name="D:\nant.git\build\net-4.0.win32\nant-
debug\bin\NAnt.Core.Tests.dll" executed="False" result="Ignored">
<test-suite type="Assembly" name="D:\test\mock-assembly.dll"
executed="True" result="Failure" success="False" time="0.047"
asserts="0">
Thanks,
Ryan
Charlie Poole
test results propogate upward and this may be an unintended consequence.
Would you please file a bug report?
Charlie
Ryan Boggs
and 2.6 that I can provide.
I will report this tonight, if not tomorrow, in the same place I
reported the last bug.
Thanks for your time. :)
Ryan