Describe the solution you'd like
Xamarin.UITest is open source and available on GitHub and accepting contributions.
Additional context
Understanding what Xamarin.UITest does can save a lot of time when something goes wrong. Having the community contributing can also make it evolve faster.
Seriously it baffles my mind that it isn't open source. There have been a number of problems that I think the community might provide some help on or just straight fix if Xamarin.UITest was open sourced.
Are there any updates on this? Has this been taken under consideration, or are there specific reasons not to change the license?
Thank you for your interest in Xamarin.UITest. We are actively investigating the possibilities to open-source the framework, but at the same time drive the project forward. Until we find the correct constellation where we can work with the community to create a better project, we will not be changing anything to Xamarin.UITest.
Making it open-source would help in getting a new momentum in adding new features, so that would be a big plus.
But I hope this would be with guidance of Microsoft, so that it would still align with the whole .Net ecosystem and the testing options for the other UI targets available.
An example I would like to have in Xamarin UI testing would be the ImageComparer Class ( https://docs.microsoft.com/en-us/dotnet/api/microsoft.visualstudio.testtools.uitesting.imagecomparer?view=visualstudiosdk-2017 ) and I guess that UITesting namespace in VS would be a great place to see what Xamarin UI testing is still missing.
One more vote to open source Xamarin.UITest... I agree with others who believe the product would benefit from having the community involved and contributing.
Another vote from me. While I was able to get Xamarin.UITest regressions integrated into our CI to trigger post-build, we sunk way to much time into it and eventually ditched them because of how difficult they were to maintain (and I'm not talking about poorly written tests.. I mean framework bugs that cause friction while writing tests).. largely due to how fragile the framework is. Perhaps it's more stable now.. but open sourcing it would really help in that regard, and actually make the product usable.
Yay vote from me too.
+1
+1
Are there any updates on this? I think the community would be very interested in hearing more about the current state of the investigation mentioned in @Oddj0b's comment.
It sure would be nice for the community to help fix bugs such as this one:
https://github.com/microsoft/appcenter/issues/1451
I'd like to port it to .NET 5 if Xamarin won't.
It will be good if it is open sourced even with out contributions. one point i have is for app.query there is invokemethod, but what are the parameters and how pass them no clue any where.we can come to know what are the methods that available and how to use them. by seing the implementation for those invoke method, we can create extensionmethods inside our project based on the reference
This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.
Thank you for your interest in Xamarin.UITest. We are actively investigating the possibilities to open-source the framework, but at the same time drive the project forward. Until we find the correct constellation where we can work with the community to create a better project, we will not be changing anything to Xamarin.UITest.
It's been nearly 2 years at this point. Has the correct constellation been found yet?
Is there any public roadmap for Xamarin.UITest? If not about open sourcing it at least about support and features?
Most helpful comment
Seriously it baffles my mind that it isn't open source. There have been a number of problems that I think the community might provide some help on or just straight fix if Xamarin.UITest was open sourced.