Test result numbers are wrong/empty

[elielia]

Running the nunit3-console (3.9) on a dll, and redirect the results to a file.
I always get that the number of tests was 45, but 0 failed, 0 passed, 0 etc., altought I see that most of the tests passed and some failed. The numbers are just wrong.

Thanks

[mikkelbu]

Hi @elielia
You'll need to provide some more information for us to help you. Can you provide what is written to screen by the console or perhaps the resulting TestResult.xml.

[elielia]

Hi, thanks for the response.
Attached a results XML that I just got.

tests-results.txt

[CharliePoole]

The result XML looks OK except for the cumulative totals. You have six tests, one failed and five passed,
but the totals in the containing suites are always 0 passed and 0 failed. That's strange!

Please tell us (1) how you are running the tests... i.e. exact command-line and (2) exactly what versions of both the framework and the runner you are using.

[mikkelbu]

I've looked into the XML and my finding are:

• Commandline is packages\NUnit.ConsoleRunner.3.9.0\tools\nunit3-console StoreKat.Infrastructure.IntegrationTests\bin\debug\StoreKat.Infrastructure.IntegrationTests.dll --result=infrastructure-integration-tests.txt
• EnsureGetForDetailOnlyReturnsAvailableSpace throws an exception, but this should not affect the cumulative totals in the other fixtures
• SpaceNotificationRepositoryTests is ignored, but there is no reason (which is required in NUnit3, so this and the name _IGNOREREASON tells me that the test project is referencing NUnit 2. Is that correct?).

Do you have any Setups, SetUpFixtureAttribute, TestFixtureSetUpAttribute .... or TearDowns in the tests?

[elielia]

You are correct.
Yes there is (I am new to this code), but seems like nothing special. Only thing can be using TransactionScope.
Any ideas?

[CharliePoole]

@mikkelbu I think you are right that the version of the framework in use is the critical thing here. It's the framework that creates the cumulative totals as well. It's not the current version because the XML for suites doesn't have total warnings and there is no start or end time on the tests. It could be V2 as you say or it could be an early NUnit 3, before we added those features.

@elielia We need to know what framework version you are using as well as what .NET runtime you are targeting with your tests in order to figure out any more.

[mikkelbu]

Closing this issue due to lack of activity. Note that we will still see new comments, so we can reopen the issue if anyone has more to add.