Ideas & Feature Requests

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

Support NUnit 3 with UITest

NUnit 3 adds a load of new features that would be useful to have, so it would be good if UITest could be updated to support NUnit 3 instead of maxing out at 2.6.4.

  • Guest
  • Sep 18 2016
Device Manufacturer
Device Model Name
Operating System Version
  • Attach files
  • Joel Shea commented
    January 12, 2017 15:58

    This is especially important if you want to do a mix of local and cloud testing.  NUnit 3 allows more flexibility that would useful in doing both with the same set of tests.

  • Bil Simser commented
    April 3, 2017 14:05

    NUnit 3 has been out since November of 2015 and this request has been sitting around for 6 months. It's one of the top ideas here so what's stopping this from moving forward?

  • Guest commented
    April 4, 2017 16:19

    I too am interested in what the hold up is. I know NUnit 3 supports async, and TestCloud doesn't play nice with async... is that it?

  • Admin
    Justin Raczak commented
    April 4, 2017 18:59

    Hi, everyone. First, I want to thank you for your patience with this issue. Next, I want to give you some context on the delay and provide you with an update.

    As you are likely aware, following Xamarin's acquisition to Microsoft, we began work on on integrating and implementing the next generation of our product within Visual Studio Mobile Center. The focus on this (very large!) project has slowed our velocity delivering value to our Xamarin Test Cloud users, which we know is not awesome. 

    At this time, our best estimate is that we'll have NUnit 3 support rolled out in the next 4-6 weeks. We will keep this ticket updated with new information should that target change. Please feel free to reach out here with any additional comments or questions. 

    Again, thank you for your patience with the less-than-awesome delay on this item.

  • Alex Tracy commented
    May 30, 2017 15:19

    Would it be possible to get an update on the status of this? Is 4-6 weeks still the expected timeline?

  • Admin
    Justin Raczak commented
    May 30, 2017 18:20

    We are still working toward this target, though are currently behind schedule. I do not have an updated delivery target just yet but will update this ticket once we do.

  • Derek Hunter commented
    July 6, 2017 16:26

    Do we have a news for this?

  • Rupal Joshi commented
    July 12, 2017 14:57

    hi @Justin Raczak - any updates on this?

  • Jeremy Craig commented
    August 6, 2017 21:00

    Hey :D Just wondering if you can share any news on progress yet?

  • Mike Hay commented
    August 15, 2017 14:20

    Just wondering if there are any updates on this?

  • Mark Bonner commented
    September 25, 2017 16:15

    The latest supported version of NUNIT is almost two years old now.  Why can't you figure out how to support it???  If you don't plan to, or you have stopped supporting the product, then please let us know.

  • karthik kk commented
    October 16, 2017 21:14

    NUnit 3.x is really very important since Specflow 2.2.x supports only NUnit 3.x, because Xamarin is not supporting NUnit 3, I have downgraded my specflow to 2.1 which has minimal features. Please support latest version of NUnit

  • Peter Simons commented
    October 19, 2017 13:40

    Is there any update on when this is going to be delivered? or any information about when work is planned to begin on this?

  • Ravi Vemula commented
    November 3, 2017 06:24

    Any update on this idea yet?

  • Gérald Hoang commented
    November 13, 2017 09:52

    Hi, any news on this ? ...

  • Gagik Kyurkchyan commented
    November 24, 2017 12:13

    We're extensively using specflow. With latest visual studio project structure changes only specflow 2.2.0 works well. It makes almost impossible to use specflow with latest visual studio and Xamarin UI tests.

  • Guest commented
    December 11, 2017 19:18

    There are so many features in NUnit 3 I *really* wish I could take advantage of. Please get this done. We are now ~30 weeks past the 4-6 week estimate. >:‑)

    App Center (previously Mobile Center) is officially out... here's hoping that freed up some dev cycles to work on this.