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 42656 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
There have been few recently added assemblies, mainly as part of netstandard, which would benefit from having unit tests added to build process.
From Sebastien: "the tests exists but we don’t have them enabled in our builds and bots".
That will happen on master and might be backported to the active/release branch afterward
@Manuel, not urgent but please look at this once you have completed the jenkins works.
To be done in master (for C10) and potentially backported to C9 (to run more tests).
PR that adds the tests (but failing) for Mono.Data.Tds can be found here: https://github.com/xamarin/xamarin-macios/pull/2580
PR that adds the tests (but failing) for System.IO.Compression.FileSystem can be found here: https://github.com/xamarin/xamarin-macios/pull/2582
PR that adds the tests (but failing) for System.IO.Compression can be found here: https://github.com/xamarin/xamarin-macios/pull/2583
New tests landed for
That's already covered. Typo for something else ?
Correct, that was a typo. System.Xml was already present.
The new missing tests are:
But we know that ->
Microsoft.CSharp -> We do not know how are tests ran, we need to talk with the mono team.
System.Data.Services -> We cannot run tests because it starts a service and we only have System.Data.Services.Client
System.Net -> missing tests.
System.Reflection.Context => missing tests.
So atm we could say we have missing ->
We are working on the System.Security tests, this might need to be landed in a diff branch since the runtime time has proposed a PR for the mono-2017-10 branch => https://github.com/xamarin/xamarin-macios/pull/2905
System.Security tests => https://github.com/xamarin/xamarin-macios/pull/2939
Updated info regarding present tests and missing ones:
Currently missing ones are:
Microsoft.CSharp.dll -> We do not know how are tests ran, we need to talk with the mono team.
System.ComponentModel.Composition.dll -> missing tests in mono. they are coming from .net core. We should run them accordingly. -> tests are present. Should find a subset of those that pass.
System.Data.Services.Client.dll -> We cannot run tests because it starts a service and we only have System.Data.Services.Client
System.IdentityModel.dll -> tests can be added. Some of the will fail. We need to find a subset.
System.Net.Http.WinHttpHandler.dll -> do not make much sense.
System.Net.dll -> missing tests in mono. they are coming from .net core. We should run them accordingly.
System.Numerics.Vectors.dll -> missing tests in mono. they are coming from .net core. We should run them accordingly.
System.Reflection.Context.dll -> missing tests in mono. they are coming from .net core. We should run them accordingly.
System.ServiceModel.dll -> some tests are present. We need to create a subset of the tests to be ran in the iOS devices. We need to find those that do not need a service running.
System.Windows.dll -> do not make much sense
System.Xml.Serialization.dll -> missing tests in mono. they are coming from .net core. We should run them accordingly.
System.ServiceModel tests added in https://github.com/mono/mono/pull/6539 and https://github.com/xamarin/xamarin-macios/pull/3238
Looked into System.Windows since it does have some classes we are interested in yet those tests have bene moved outside mono.
Same with System.ServiceModel.internals.
System.IdentityModel will be added. One test is added in iOS and Mac Modern and 158 on mac full.
Microsoft.CSharp.dll - many xunit tests are available in mono
System.ComponentModel.Composition.dll - no tests and nothing planed in the short term
System.Net.Http.WinHttpHandler.dll - ok to ignore
System.Net.dll - forwarding assembly, ok to ignore
System.Numerics.Vectors.dll - many xunit tests are available in mono
System.Reflection.Context.dll - ok to ignore, the code will be NIE anyway
System.Xml.Serialization.dll - forwarding assembly, ok to ignore
PR for System.IdentityModel -> https://github.com/xamarin/xamarin-macios/pull/3295
Taking into account Marek comments and the new added tests, we have to get the following assemblies to run the unit tests since we do not have more assemblies to be added using nunit after landing https://github.com/xamarin/xamarin-macios/pull/3295
Present tests (NUnit)
System.Data.Services.Client -> Will take a look if a subset of the tests can be ran on devices.
About the xnunit test. They are extensions to existing nunit tests (they cover different code) and the goal is to have xunit tests for all assemblies. Right now we have about 6 but the end goal is to have many more
System.Data.Services.Client => Seems not to have tests present in mono:
[ERROR] FATAL UNHANDLED EXCEPTION: System.IO.FileNotFoundException: Could not find file "/Users/mandel/Xamarin/macios/master/xamarin-macios/external/mono/mcs/class/System.Data.Services.Client/System.Data.Services.Client_test.dll.sources"
@marek yes, I know about the xunit goals we will make that harness is ready for that goal :)
Great, let's do the xunit ones from mono-2017-12 (mono 2017-10) and land them, one by one, once we have bumped to the new mono