Make Xamarin.UITest open source

akamud commented 5 years ago

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.

dansiegel commented 5 years ago

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.

lukasjuhrich commented 4 years ago

Are there any updates on this? Has this been taken under consideration, or are there specific reasons not to change the license?

Oddj0b commented 4 years ago

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.

Depechie commented 4 years ago

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.

jbachelor commented 4 years ago

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.

winnicki commented 4 years ago

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.

kfuller010 commented 4 years ago

Yay vote from me too.

MaximMikhisor commented 4 years ago

+1

pooter07 commented 3 years ago

+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.

Soundman32 commented 3 years ago

It sure would be nice for the community to help fix bugs such as this one: https://github.com/microsoft/appcenter/issues/1451

MihaMarkic commented 3 years ago

I'd like to port it to .NET 5 if Xamarin won't.

ajay-kopperla commented 3 years ago

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

ghost commented 3 years ago

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.

Soundman32 commented 3 years ago

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?

johannperez commented 2 years ago

Is there any public roadmap for Xamarin.UITest? If not about open sourcing it at least about support and features?

DamianSuess commented 2 years ago

Let's not let this puppy go stale. If MS won't open source it, it may require a startup to make a C# clone of it.

dansiegel commented 2 years ago

FWIW, an important consideration at this point is that the .NET Maui team announced earlier this year that Maui would not be using Xamarin.UITest going forward and would instead be looking for an Appium based approach.

you can run Xamarin.UITest against a .NET 6 MAUI app.

Building UITests as a .NET 6 project is a different topic. @DimahZaid @ryanjsalva fyi #dotnetmaui will use Appium. @DanJSiegel started a project here https://t.co/xoFKusgvee that you may be interested in.
— David Ortinau (@davidortinau) February 19, 2021

For those who are looking for an OSS solution to UI Testing your Xamarin / Maui apps, you may want to check out the Xappium project.

DamianSuess commented 2 years ago

Thank you, @dansiegel, that is good to know. Who knows, you may see a PR coming your way ;)

bruno-garcia commented 2 years ago

The reason I was hoping this would get open sourced is that this is the only way to write tests in C# for AppCenter. So if I want to write Appium tests a single code base (in C#) to test apps in iOS/Android and desktop apps, I'll need to write Java.

The issue requesting support for Appium with a C# driver is another one ignored for years. Same as the issue asking for line numbers in crash reports for Xamarin. I serious wonder why appcenter even has a GitHub org. It just becomes the place you go to get frustrated with being ignored.

EDIT: Just realized sourcelabs support Appium with C# tests, has more real devices and costs less.

ghost commented 2 years ago

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.

lukasjuhrich commented 2 years ago

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.

Bump for obvious reasons.

ghost commented 2 years ago

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.

MaximMikhisor commented 2 years ago

Please open source it!