Bug 52326 (vs-504800) - Not all tests are runnable from Unit Tests pad
Summary: Not all tests are runnable from Unit Tests pad
Alias: vs-504800
Product: Xamarin Studio
Classification: Desktop
Component: NUnit (show other bugs)
Version: 6.2.0 (C9)
Hardware: PC Mac OS
: Highest normal
Target Milestone: 15.7
Assignee: Bugzilla
Depends on:
Reported: 2017-02-06 17:53 UTC by Stephen Shaw
Modified: 2018-01-25 15:05 UTC (History)
1 user (show)

Tags: vs-sync
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 52326 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Stephen Shaw 2017-02-06 17:53:59 UTC
Not all of the nodes in the Unit Tests pad will trigger tests to be run. Or if they are there is no indication that they are or have run.

Typically these are specific tests or a group of TestCases or sometimes even a file of tests (class).
Comment 1 Lluis Sanchez 2017-02-06 18:00:26 UTC
I created a unit test library with several levels of nodes and the tests run from whatever node I click on. Which solution has this problem?
Comment 2 Stephen Shaw 2017-02-06 18:01:42 UTC
this is md-addins. Specifically Xamarin.AndroidDesigner.Tests and MonoDevelop.MonoDroid.Tests.

I hit this fairly regularly
Comment 3 Lluis Sanchez 2017-02-06 18:05:39 UTC
Ok, I can repro.