e76440c53e
GameDetailViewModel resolves INavigationService from DI, and GameDetailView.axaml references the MultiplyConverter declared in the real App.axaml. Neither was present in the test harness, so both GameDetailView layout tests threw before producing a screenshot. Register the real NavigationService and mirror the MultiplyConverter into TestApp so the views render. Baselines still need a fresh CI capture since these tests never previously rendered. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
16 lines
745 B
XML
16 lines
745 B
XML
<Application xmlns="https://github.com/avaloniaui"
|
|
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
|
|
xmlns:converters="using:LANCommander.Launcher.Converters"
|
|
x:Class="LANCommander.Launcher.Tests.TestApp"
|
|
RequestedThemeVariant="Dark">
|
|
<Application.Styles>
|
|
<FluentTheme />
|
|
</Application.Styles>
|
|
|
|
<!-- Converters that views resolve from the application's resource scope.
|
|
The real App.axaml declares these globally; mirror only what the views
|
|
under test require so unstyled baselines stay otherwise unchanged. -->
|
|
<Application.Resources>
|
|
<converters:MultiplyConverter x:Key="MultiplyConverter" />
|
|
</Application.Resources>
|
|
</Application>
|