Display NUnit "message" for Inconclusive #33

Closed
espenalb opened this Issue Dec 29, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@espenalb
Collaborator

espenalb commented Dec 29, 2015

The following test case:

<test-case id="0-1475" name="FlashTestLocationShouldIncrementOnEachTick" fullname="SensorSimulatorTests.Tests.Integrity.DiagCycleRamFlashTests.FlashTestLocationShouldIncrementOnEachTick" methodname="FlashTestLocationShouldIncrementOnEachTick" classname="SensorSimulatorTests.Tests.Integrity.DiagCycleRamFlashTests" runstate="Runnable" seed="1460000646" result="Inconclusive" start-time="2015-12-29 07:34:53Z" end-time="2015-12-29 07:34:53Z" duration="0.233112" asserts="0">
<properties>
<property name="Category" value="MergeTests"/>
</properties>
<reason>
<message>
<![CDATA[ Cannot execute test, do not know firmware size... ]]>
</message>
</reason>
<output>
<![CDATA[
2015-12-29T08:34:53.476:Debug:DiagCycleR: --------------- Test starting ---------------
 2015-12-29T08:34:53.476:Debug:SENSORTEST: WR: Write:0xFF-SERVICE_UA-0x01(
 2015-12-29T08:34:53.710:Debug:DiagCycleR: --- TearDown -----
 2015-12-29T08:34:53.710:Debug:DiagCycleR: --- TearDown complete -----
]]>
</output>
</test-case>

Is displayed as
image

It would be very helpful if the message was displayed above the console output... 😄

@anshooarora

This comment has been minimized.

Show comment
Hide comment
@anshooarora

anshooarora Dec 29, 2015

Member

Espen, sure. I will try to do it soon as I am out.. But if you get a chance before me, you can add this feature in and send me a pull request.

The output comes from the following line:

https://github.com/reportunit/reportunit/blob/master/ReportUnit/Parser/NUnit.cs#L207

Member

anshooarora commented Dec 29, 2015

Espen, sure. I will try to do it soon as I am out.. But if you get a chance before me, you can add this feature in and send me a pull request.

The output comes from the following line:

https://github.com/reportunit/reportunit/blob/master/ReportUnit/Parser/NUnit.cs#L207

@anshooarora

This comment has been minimized.

Show comment
Hide comment
@anshooarora

anshooarora Jan 4, 2016

Member

Feature added in d4440db

Member

anshooarora commented Jan 4, 2016

Feature added in d4440db

@anshooarora anshooarora closed this Jan 4, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment