3 Commits

Author	SHA1	Message	Date
copilot-swe-agent[bot]	e809567010	Improve test documentation to clarify they verify the fix ... - 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>	2025-11-16 00:19:02 +00:00
copilot-swe-agent[bot]	f1a6534dca	Rewrite integration tests to actually run scenarios ... - 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>	2025-11-15 21:28:13 +00:00
copilot-swe-agent[bot]	0d6debde63	Add integration tests for ForceDriver persistence ... - 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>	2025-11-15 21:13:50 +00:00