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 24354 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
It would be nice to have an easy way to set the remote server options in code so that you don't have to click on the UI to open and set the Options to send the test results to a remote server in an Android NUnit runner project.
## Workaround option
Use Xamarin.UITest and automate the UI to open the Options page and set the values. This will only work on a simulator unless you have a test cloud account to allow testing on a device.
Additionally : not only the remote server options but also tests results output format like "NUnit2XmlOutput", "NUnit3XmlOutput".
Changing from enhancement to normal as , IIRC, it was said there was no reason for these classes to be internal.
The classes that should be made public, IMO, are:
With the above classes public, the user should be able to easily set the remote server options in code (like can be done with Monotouch.NUnitLite) and provide a custom text writer to get the results in the desired format.
You don't have to open any UI to set those options. "remote", "hostName" and "hostPort" can be specified when you launch the app through standard Android instrumentation. That's what our QA team does.
The reason why I didn't make them open is that any stable API will be then required to remain even after we make significant changes (the most foreseeable one is to migrate to NUnit3 once it gets released).