Is it possible to add a test? also can you create a issue associated with this?

Unfortunately the template tests only create, build, and maybe publish the templates. None of the tests run the apps built by the template. It's certainly possible (somehow), but we don't do it at this time. I think you'd need to do that in order to test this?

We could check the new template for the line

We could check the new template for the line

We could... but that's pretty random. Why check this one thing but not anything else?

What else can we check? We would have to set up a template and then run it and then somehow communicate with the running ap to determine which handler is in use.

What else can we check? We would have to set up a template and then run it and then somehow communicate with the running ap to determine which handler is in use.

Yeah I think that's the only meaningful way to test it. I'm not at all saying it's easy: it's probably not.

A pattern I've seen before is to:

1. Instantiate the template (dotnet new <stuff>)
2. Add a little bit of instrumentation to it to make the app more 'inspectable', so like add TestInspector.cs to it that has magic code to 'test' things in the app (say, a check to make sure the right handler is actually registered, or that a font is installed, or that all controls have accessible descriptions, etc.)
3. Run the app
4. Have the test call into the TestInspector.cs functions to verify stuff

But if the test is just to check that the template output contains a string, I wouldn't even bother. It's not verifying the code is correct or even executed at all, let alone if it has the desired effect in the running app. And on top of that it's a very fragile test because a lot of changes that could be good changes could cause this test to fail (say we change MAUI to have this be built-in and not needed in the template, this test could start failing, even though there's nothing wrong).

/rebase

The handler registration is temporary and will be the default at some point soon. Also, I am testing the template result, not whether it is used. I can make a more complex test, but I don't think it is worth it because it is all going away soon.

/rebase