<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Christoph,<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On May 20, 2022, at 5:00 AM, <a href="mailto:christoph.thiede@student.hpi.uni-potsdam.de" class="">christoph.thiede@student.hpi.uni-potsdam.de</a> wrote:</div><br class="Apple-interchange-newline"><div class="">With InvalidDirectoryError, we have one more exception class that overrides #defaultAction to handle itself silently without bringing up a debugger. As a consequence, some tests that reproduce normal user interactions will fail for no visible reason. See DirectoryChooserDialogTest>>testChooseAbsentDirectory in <a href="https://lists.squeakfoundation.org/pipermail/squeak-dev/2022-May/220634.html" class="">polish-file-dialogs.3.cs</a> for an example.<br class="">
<br class="">
I am unsure how to deal with these situations: Isn't an error that doesn't bring up a debugger some kind of anti-pattern? </div></blockquote><div><br class=""></div><div><div>I usually think of these as decisions that were made to support end-user experience in Squeak. In this case, perhaps it supports hard-coded paths that live within older release images and/or VM builds on various platforms. Or maybe it made loading image segments smoother...</div><div class=""><br class=""></div></div><blockquote type="cite" class=""><div class="">Should we rethink the definition of this exception class?</div></blockquote><br class=""></div><div>If it's now possible to give a test designer the choice of whether to handle the exception or not, that sounds like a win...</div><div><br class=""></div><div><br class=""></div><div>Best,</div><div>Tim</div><div><br class=""></div><div><br class=""></div><div><br class=""></div></body></html>