Home → Suggestions →

Inconclusive tests currently show up as errors

• Edit

John Batte

22 Oct, 2013 08:14 PM

When a unit test result is "inconclusive" (neither passing nor failing; most commonly seen with SpecFlow-driven test assemblies), AppVeyor shows this status as "error". AppVeyor should recognize a "pending" or "inconclusive" build status and map correctly to it.

1. Support Staff 1 Posted by Feodor Fitsner on 22 Oct, 2013 08:16 PM

   

   Hi John,

   What testing framework is it?

   -Feodor

   • Edit

2. 2 Posted by John Batte on 22 Oct, 2013 09:32 PM

   

   Hi,

   I can reproduce this with NUnit + SpecFlow.

   -j

   • Edit

3. Support Staff 3 Posted by Feodor Fitsner on 23 Oct, 2013 03:15 AM

   

   OK, will take a look. Thanks for reporting on this!

   -Feodor

   • Edit

4. 4 Posted by r.baeriswyl on 13 Mar, 2017 06:52 AM

   

   This seems still to be an issue.
   I get a lot of messages like:

   Error processing test event: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at System.Collections.Concurrent.ConcurrentDictionary`2.get_Item(TKey key) at Appveyor.NUnit3Logger.AppveyorTestEventListener.TestFinished(XElement testCase) at Appveyor.NUnit3Logger.AppveyorTestEventListener.OnTestEvent(String report) Test event element: <test-case id="1-1097" name="ThreeWayToggleTest"

   Will this be addressed somewhen?

   • Edit

5. 5 Posted by Ilya Finkelshte... on 13 Mar, 2017 08:46 PM

   

   @r.baeriswyl could you please provide a repro in public repository?

   • Edit

6. 6 Posted by r.baeriswyl on 14 Mar, 2017 05:30 AM

   

   Sure:
   https://ci.appveyor.com/project/RomanBaeriswyl/flaui

   • Edit

7. 7 Posted by r.baeriswyl on 20 Mar, 2017 09:10 AM

   

   Any news on this issue?

   • Edit

8. Support Staff 8 Posted by Feodor Fitsner on 21 Mar, 2017 12:33 AM

   

   Should be fixed now.

   • Edit

9. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:15 AM.