We use MSTest under TFS (2008). The big advantage is that it runs tests on a real device (we run both against emulators and physical devices), and testing is performed from the server, and not from the device. This means that you do not need to select tests to run, etc. From the device user interface (a la CFNUnitBridge), which is painfully inconvenient and does not contribute to continuous integration.
However, MSTest is not a cure. This has some serious flaws (for example, debugging tests are really painful, and running the test is slow), but it is better than everything we tried. The hope is that as MS moves forward, usability will improve, and we will be able to continue working on the existing test platform.
Using anything else, we consider it too risky, since many device frameworks and libraries tend to fade and die without any major sponsor. For example, NUnitLite had only 477 downloads and very few code or activity crashes for two years at this post - this does not inspire confidence that it will grow in functions.
ctacke
source share