Number of asserts in XML result file always stays 0

Bug #684598 reported by Mario Peeters
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit V2
Fix Released
High
Charlie Poole

Bug Description

Environment:
nunit-version="2.5.8.10295"
clr-version="2.0.50727.3615"
os-version="Microsoft Windows NT 5.1.2600 Service Pack 3"
platform="Win32NT"

Description:
When I'm generating an xml report via the console runner, the number of asserts always stay 0. The issue seems to be linked with the nunit-console parameter /timeout. When this option is used the resulting xml file always has the number of asserts 0

Scenario:
- Build the Debug configuration of the following solution in the "samples\csharp" folder of the nunit distribution: "CSharp.sln"
- Open a DOS terminal
- Go to the "samples\csharp\failures\bin\Debug" folder of the nunit distribution
- Execute the following command:

  nunit-console /xml=results.xml cs-failures.dll

-> in the resulting xml (results.xml) the correct number of asserts are shown e.g.:

    <test-case name="NUnit.Samples.SimpleCSharpTest.Equals" executed="True" result="Failure" success="False" time="0.000" asserts="5">

- repeat the command with the following options:

  nunit-console /timeout=5000 /xml=results.xml cs-failures.dll

-> in the resulting xml (results.xml) the number of asserts are always 0 e.g.:

    <test-case name="NUnit.Samples.SimpleCSharpTest.Equals" executed="True" result="Failure" success="False" time="0.000" asserts="0">

If the scenario is repeated with another version of NUnit (e.g: 2.5.2.9222), the issue is not seen

Related branches

Revision history for this message
Mario Peeters (mario-peeters) wrote :
Revision history for this message
Charlie Poole (charlie.poole) wrote :

Appears related to bug #684821

Changed in nunitv2:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Charlie Poole (charlie.poole)
milestone: none → 2.5.9
Changed in nunitv2:
status: In Progress → Fix Committed
Changed in nunitv2:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.