nunit-core team mailing list archive

[Mario Peeters <684598@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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

** Affects: nunitv2
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/684598

Title:
  Number of asserts in XML result file always stays 0

Status in NUnit V2 Test Framework:
  New

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