Ideas & Feature Requests

Share your ideas on how Test Cloud can better help you deliver higher quality apps faster.

Support Inconclusive in Nunit

Well I mean other than all the reasons it was added to nunit (of which there are many) we are now marking our tests that fail to start the app as inconclusive since 99 times out of 100 this means the app wasn't launched and not that it crashed on startup (we get nothing about a crash in Insights).

Currently test cloud reports these tests as success, which is better than reporting them as failed, but ideally they would be treating uniquely

  • Guest
  • Mar 9 2016
Device Manufacturer
Device Model Name
Operating System Version
  • Attach files
  • Alan McGovern commented
    March 9, 2016 20:57

    I use these all the time to disable tests which fail as soon as a new iOS beta comes out. That gives me a green baseline to make sure i don't regress anything as i fix the failing tests:

     

    if (iOS >= NewBeta) Assert.Inconclusive ("Fix this under new iOS!");