Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 6233 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
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
The solution changes view should show results of syntax checking/compilation, source analysis and (maybe) test runs for every changed file.
This would make warnings and broken tests less likely to slip through when preparing to commit code.
I imagine this could be visualized as a couple of colored fields showing the status, one for tests, one for compilation and one for other static analysis. The test status would only apply for files containing a TestFixture.
An even cooler behaviour for test cases:
For any file, find the test cases that execute any code in it.
Combine the results of those test cases into a single value in the same way they are combined in the test tree view.
Implementation idea for that would be to integrate collection of code coverage statistics in the NUnit addin in a way such that the data can be made available to other addins.