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 on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
In Release notes:
The tests pad now shows results from previous runs.
To check this note, I have created 'NUnit Library Project' under C#. Application build successfully. If we try to debug the application it gives popup with message 'An application is already running and will have to be stopped it. Do you continue?'.
Screen cast: http://www.screencast.com/t/e7xe93Wq7
We are sure whether we are doing correct or not? If I am doing wrong, please provide some steps to check this.
XS 4.0.11(build 6)
Mono 3.2.1 ((no/f3f789e)
I see the same behavior when I set the Unit test project as a startup project and attempt to run from the normal run action. This is likely a separate bug from the new unit test result.
Every attempt to run the unit test results in Xamarin studio reporting a process is still running.
That being said, I *also* don't seem to see anything that's different in the Unit test add-in related to historical results.
Here's the behavior on 4.0.10: http://screencast.com/t/6PLEXf5z3ql
Here's the behavior on 4.0.11: http://screencast.com/t/DrKUZJuRw
Mike is this something you added? Can we get a better description of what should be changed here?
No it's not something from me.
The sceencasts show the new behavior btw.
Just look what happens to the tests you don't run. They show the old results in a light color - that's the feature.
Ahh, from the note I assumed that it was more than just the single most recent result - something related to gathering longer term data. I was focusing in on the results pad.
Thanks for clarifying and pointing it out.