What problem does it solve? FlaUI tests that drive WPF applications from a separate process often fail silently: Mouse.Down does nothing, drag-and-drop is ignored, clicks hit the wrong element, or tests pass individually but fail when run together. This Skill identifies the root causes — stuck keys, SetCursorPos hit-test gaps, xUnit parallel execution, and incorrect canvas coordinates — and provides concrete fixes. ## Core Features & Use Cases - Stuck-key diagnosis and release: Detect keys left pressed by Keyboard.Press and release them with ReleaseAllKeys or ReleaseModifierKeys before mouse gestures. - SendInput-based mouse injection: Replace SetCursorPos with SendInput MOVE/ABSOLUTE events so WPF hit tests update correctly, including atomic move-and-click sequences. - Drag interpolation tuning: Fix adorner flickering during drags by adjusting step counts, sleep intervals, and routing paths around interactive zones. - xUnit parallelization control: Configure xunit.runner.json to disable parallel execution so tests do not fight over shared mouse and keyboard state. - Use Case: A FlaUI xUnit test drags a connector in a Nodify-based WPF editor but the gesture is silently rejected; this Skill walks through the diagnostic checklist, identifies a stuck DELETE key from Keyboard.Press, and fixes it by switching to Keyboard.Type plus ReleaseModifierKeys. ## Quick Start Ask the assistant to diagnose why your FlaUI Mouse.Down or drag gesture is silently failing on a WPF control and apply the appropriate fix.