[Cuis-dev] Unavailable SUnit TestResource stops test runner

[Jon Raiford]

Hi Hernán,

I can confirm that this patch works great for me. Thank you again.

(Fwiw, I meant UnhandledError before, not UnhandledException – in SUnitNameResolver class>>errorObject)

Jon

From: Cuis-dev <cuis-dev-bounces at lists.cuis.st> on behalf of Jon Raiford via Cuis-dev <cuis-dev at lists.cuis.st>
Date: Thursday, August 8, 2024 at 9:26 AM
To: Hernán Wilkinson <hernan.wilkinson at 10pines.com>, Discussion of Cuis Smalltalk <cuis-dev at lists.cuis.st>
Cc: Jon Raiford <raiford at labware.com>, Juan Vuletich <juan at cuis.st>
Subject: Re: [Cuis-dev] Unavailable SUnit TestResource stops test runner
Hi Hernán,

Thank you! I will give this a try. Also, good catch on the exception problem. I forgot that I worked around this by changing the reference to UnhandledException back to Error, which is how other SUnit implementations seem to work. I agree that UnhandledException is more appropriate so it is nice that you took care of that.

Jon

From: Hernán Wilkinson <hernan.wilkinson at 10pines.com>
Date: Wednesday, August 7, 2024 at 7:51 PM
To: Discussion of Cuis Smalltalk <cuis-dev at lists.cuis.st>
Cc: Juan Vuletich <juan at cuis.st>, Jon Raiford <raiford at labware.com>
Subject: Re: [Cuis-dev] Unavailable SUnit TestResource stops test runner
Hi,
 I agree, it is better to do that.
 Attached is a change set that implements that behavior.
 BTW, there was an error when a resource was not available because it was trying to debug an UnhandledError without an unhandled exception. I fixed that by making the not availability of a resource to fail and not to error.

 I'll send another change set soon because #debugAsFailureIfCanNot: does not make sense anymore because quick methods can be debugged.

 Cheers!
 Hernan.

On Wed, Aug 7, 2024 at 4:39 PM Juan Vuletich via Cuis-dev <cuis-dev at lists.cuis.st<mailto:cuis-dev at lists.cuis.st>> wrote:
On 8/6/2024 11:43 AM, Jon Raiford via Cuis-dev wrote:
I have a question for the SUnit experts out there. Have a look at this simple test case that demonstrates an unavailable test resource. I don’t understand why an unavailable test resource causes the test runner itself to stop. Wouldn’t it be more correct to flag all test cases that rely on it as failed instead? Ideally we should be able to run automated tests without having to worry about this stopping the testing framework,

Thanks,
jon

I agree. I think an unavailable test resource is quite like a test failure, or an error (DNU for instance). These don't stop the test run, and they are counted for the suite result.

Does anybody have a good reason to open a debugger?

Thanks,

--

Juan Vuletich

cuis.st<http://cuis.st>

github.com/jvuletich<http://github.com/jvuletich>

researchgate.net/profile/Juan-Vuletich<http://researchgate.net/profile/Juan-Vuletich>

independent.academia.edu/JuanVuletich<http://independent.academia.edu/JuanVuletich>

patents.justia.com/inventor/juan-manuel-vuletich<http://patents.justia.com/inventor/juan-manuel-vuletich>

linkedin.com/in/juan-vuletich-75611b3<http://linkedin.com/in/juan-vuletich-75611b3>

twitter.com/JuanVuletich<http://twitter.com/JuanVuletich>
--
Cuis-dev mailing list
Cuis-dev at lists.cuis.st<mailto:Cuis-dev at lists.cuis.st>
https://lists.cuis.st/mailman/listinfo/cuis-dev<https://lists.cuis.st/mailman/listinfo/cuis-dev>


--
Hernán Wilkinson
Agile Software Development, Teaching & Coaching
Phone: +54-011-4893-2057
Twitter: @HernanWilkinson
site: http://www.10Pines.com<http://www.10pines.com/>
Address: Alem 896, Floor 6, Buenos Aires, Argentina
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20240808/7d853b7a/attachment.htm>