On Thu, 18 Apr 2024 17:57:42 GMT, Oliver Kopp <d...@openjdk.org> wrote:
> Based on my experience, I would create a test for `WinTextRangeProvider` > directly and supply some values to it to check that the "right" branches are > covered. Based on what I see from the stacktrace, this sounds good. We now know that the methods in WinTextRangeProvider can be invoked with bogus values. A good test would invoke those methods with bogus values and detect a non-catched Exception before, and no Exception after the patch. This can easily be done with a unit test, no need to fire up a minimal app. ------------- PR Comment: https://git.openjdk.org/jfx/pull/1442#issuecomment-2065944318
