- Added SetupForceDriverConfig() and ReloadForceDriverConfig() methods to UICatalog.cs
- These methods contain the fix logic (parts 1 and 2)
- Made methods internal and added InternalsVisibleTo for IntegrationTests
- Updated UICatalogMain and scenario loop to use these methods
- Updated tests to call UICatalog's methods instead of duplicating the logic
- Tests now fail without the fix and pass with it, proving they test the actual UICatalog code
- All 91 UICatalog integration tests pass
Co-authored-by: tig <585482+tig@users.noreply.github.com>
- Added detailed comments explaining the fix has two parts
- Part 1: Set ForceDriver in RuntimeConfig (in UICatalogMain)
- Part 2: Reload RuntimeConfig before each scenario (in scenario loop)
- Tests simulate both parts and verify driver persists
- Added note that commenting out the reload causes the test to fail, demonstrating the bug
Co-authored-by: tig <585482+tig@users.noreply.github.com>
- Tests now use UICatalogTop and call scenario.Main()
- First test simulates full UICatalog flow: run UICatalogTop, select scenario, run scenario
- Second test runs multiple scenarios in sequence to verify driver persistence
- Both tests properly clean up event handlers to avoid assertions
- Tests verify the fix works correctly by actually running scenarios
Co-authored-by: tig <585482+tig@users.noreply.github.com>
- Created ForceDriverTests.cs with two integration tests
- Tests verify ForceDriver persists across Init/Shutdown cycles
- Tests verify scenarios use ForceDriver when calling Application.Init()
- Both tests pass successfully
Co-authored-by: tig <585482+tig@users.noreply.github.com>
