Correct MIC source mapping for E‑Test/Vitek and add regression coverage for Voriconazole dropdowns

[Copilot]

Reported behavior: E‑Test rows (notably Voriconazole) could display MIC options that match Vitek-style lists for certain row combinations. This points to a method/agent mapping inconsistency in breakpoint-driven dropdown population.

• Configuration mapping correction

  • Fixed an incorrect antifungal key in NRZMyk.Services/Configuration/BreakpointSettings.json under MicSteps.Vitek.
  • The key was Fluorouracil but the configured value set belongs to Flucytosine, which breaks enum-keyed mapping consistency used by MIC lookup.

• Regression test for the reported UI symptom

  • Added a component-level regression test in NRZMyk.Components.Tests/Pages/SentinelEntryPage/CreateTests.cs that models mixed Vitek/E‑Test Voriconazole rows and row removal.
  • The test asserts the remaining E‑Test Voriconazole row keeps E‑Test MIC options and does not drift to Vitek options.

• Test fixture support for method-specific MIC data

  • Added a method-specific test IMicStepsService implementation in the test file to explicitly separate Vitek vs E‑Test Voriconazole MIC lists and make the regression deterministic.

// BreakpointSettings.json (MicSteps.Vitek)
- "Fluorouracil": [ ... ]
+ "Flucytosine": [ ... ]

eTestMicValues.Should().Contain("≤0,008");
eTestMicValues.Should().Contain("0,06");
eTestMicValues.Should().NotContain("≤0,12");

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud