I try this project to the default mauiapp template by Visual Studio 2022 (v17.4.1).

I set the button of "MainPage.xaml" and its' AutomationId is "CounterBtn".

UITest code is:

await driver.AutomationId("CounterBtn").Tap();

When I set

MainPage = new MainPage(); 

at App.xaml.cs, it can work will.

But when I set

MainPage = new AppShell();

at App.xaml.cs and AppShell.xaml is:

<Shell
    x:Class="MauiApp2.AppShell"
    xmlns="http://schemas.microsoft.com/dotnet/2021/maui"
    xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
    xmlns:local="clr-namespace:MauiApp2"
    Shell.FlyoutBehavior="Disabled">
    <ShellContent
        Title="Home"
        ContentTemplate="{DataTemplate local:MainPage}"
        Route="MainPage" />
</Shell>

it can't work and I got the following error messages:

Error: Microsoft.Maui.Automation.ElementsNotFoundException: Elements not found matching query
   at Microsoft.Maui.Automation.Querying.DriverQuery.AutoWait(Int32 autoWaitMs, Int32 retryDelayMs, Boolean waitForNone)
   at Submission#9.<<Initialize>>d__0.MoveNext()
--- End of stack trace from previous location ---
   at Microsoft.CodeAnalysis.Scripting.ScriptExecutionState.RunSubmissionsAsync[TResult](ImmutableArray`1 precedingExecutors, Func`2 currentExecutor, StrongBox`1 exceptionHolderOpt, Func`2 catchExceptionOpt, CancellationToken cancellationToken)

If it supports Shell and Shell navigation, how should I do for my UITest code?

Would you take a minute to help a soul in pain?

Whilst Android works, my configuration does not work in Windows.
Using this:

driver = new AppDriverBuilder()
.AppId("com.companyname.samplemauiapp")
.AppFilename("C:\Users\mdelg\source\repos\Maui.UITesting\samples\SampleMauiApp\bin\Debug\net7.0-windows10.0.19041\win10-x64\SampleMauiApp.exe")
.DevicePlatform(Platform.Winappsdk)
.AutomationPlatform(Platform.Maui)
.Build();
}

I get this error:

System.InvalidOperationException: 'The system cannot find the file specified'

In this instruction
Session = new Lazy<WindowsDriver>(() =>
new WindowsDriver(new Uri("http://127.0.0.1:4723"), appCapabilities));

that in the debugger passes the first time and then throws the error after this instruction
await driver. Start();

Any idea? Is it configuration or Windows Application Driver (installed and using ve. 1.2.1.0)

Thanks in advance and I think your package could solve a great need for the Maui community.

I cloned the repo, built the app and updated the settings in Tests.cs to point to my APK and device (Samsung Galaxy Tab S5e on Android 11). I then created the test below and when I run the test it launches the app on the tablet but when attempting to perform InputText it switches out of the app and basically does a google search.

[Fact]
public async Task LoginTest()
{
await driver.Start();
await driver.AutomationId("entryUsername").InputText("xamarin");
await driver.AutomationId("entryPassword").InputText("1234");
await driver.AutomationId("buttonLogin").Tap();
}

Any suggestions as to what to do to try to troubleshoot this?

I tried to implement your nice package but my project is already running in .Net 7 and was more pain than pleasure. Had to abandon.

Was wondering if you have any plans to port it to .Net7 or have an option for UI test instead?

Thanks in advance

Right now the server starts from that sample app, is there a way that you though of to start the server so that we can test any random app with it? I have cloned it and working on cli yaml runner but it doesn't work with other apps.

Any news on the status of the project? Since there is no official solution for testing

As title states, what's the future of MAUI UI testing?
Will this repo be eventually used for UI testing or are we going to keep using Appium?

Hello,

If my understanding is correct, in order to be able to test the application you'll need to include the agent in the application code itself (e.g., <ProjectReference Include="..\..\src\Agent\Agent.csproj" /> from here)

I'd say this is a significant drawback, since ideally you'd want to test exactly the same binary that you also manually smoked tested and that you'll ship on the App Store/Play Store, and you wouldn't want to include the agent in the store binary. Testing the same binary gives you increased confidence, as it reduces the risk introduced by the differences between the "test" binary and the store binary.

This is why Appium has been our tool of choice for a long time, because you test the same binary that you ship on the store.

Regards,
Cosmin

How to setup Xappium for testing a .Net Maui iOS app? Please help with step by step instructions.

It would be great to test Maui application in isolation from backend in some cases. Therefore, the ability to replace services in DI container with mocks would be useful. Usually that applies to Http clients, but other things are possible as well.
I'm not sure if that's possible with the current approach though.
Are there any ideas how that could be achieved?

https://github.com/dotnet/xharness

With dotnet developing XHarness, would this project be replaced?