FlightTests: the combat-exit test removes every listing of the engaged track

The grudge lists the track in VisibleEnemies a second time (the hostility refresh adds it again), so a single Remove left it visible.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Meta Vens 2026-10-16 20:58:26 +02:00
commit 807533d26b

View file

@ -654,9 +654,10 @@ public sealed class FlightTests : IDisposable
Assert.Same(hot, member.Target.Value.Entity);
UpdateUntil(minion, () => CurrentState(minion) is CombatState);
member.VisibleEnemies.Remove(hot);
// The grudge listed it a second time (the hostility refresh adds it again), so every listing goes.
while (member.VisibleEnemies.Remove(hot)) { }
Tick(.1f);
Assert.True(member.Target.Value.IsNone, "Target is hot " + ReferenceEquals(member.Target.Value.Entity, hot) + ", held " + _zone.Flights.Single().PhaseOf(held) + ", hot " + _zone.Flights.Single().PhaseOf(hot) + ", visible " + member.VisibleEnemies.Count);
Assert.True(member.Target.Value.IsNone);
Assert.IsType<FollowTask>(minion.Task);
UpdateUntil(minion, () => !(CurrentState(minion) is CombatState));
UpdateUntil(minion, () => CurrentState(minion) is FollowState);