Yes. Also you can try extending the current commands to get your âDebug Testsâ from the class side. And we accept contributions :)
El 8 ene. 2024, a las 14:31, Gabriel Cotelli <g.cotelli@gmail.com> escribió:
You can implement another version of TestResult that halts when an error is added instead of recording it, and reimplement classForTestResult in the test cases to return this new class instead.
On Mon, Jan 8, 2024 at 5:54â¯AM Davide Varvello via Pharo-users <pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org>> wrote: No ideas?
Cheers Davide
On Thursday, January 4, 2024 at 03:42:17 PM GMT+1, Davide Varvello via Pharo-users <pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org>> wrote:
Hi Noury,
You are right and reading your answer I understand I wasn't crystal clear.
I have a test scenario where sometimes a race condition occurs, so I'm not expecting any error. Which is why I'd prefer something built-in Pharo: a sort of "haltIfError" or "haltOnError" built-in command. Is there anything like that in Pharo?
TIA
Davide
On Thursday, January 4, 2024 at 01:24:59 PM GMT+1, Noury Bouraqadi <bouraqadi@gmail.com <mailto:bouraqadi@gmail.com>> wrote:
Hi Davide,
Why not use one of the following:
self should: ["message that might signal an error"] raise: Error "Replace Error with the exception you want to catch" self shouldnt: ["message that might signal an error"] raise: Error "Replace Error with the exception you want to catch"
On Jan 3 2024, at 4:55 pm, Davide Varvello via Pharo-users <pharo-users@lists.pharo.org <mailto:pharo-users@lists.pharo.org>> wrote: Hi Guys,
Sometimes I'd like to stop my test suite when an error occurs.
My raw approach is to put a self halt in the TestResult>>addError: and look at the debugger, but I'm wondering if there is a more suitable way.
Can you help me, please?
TIA Davide
