No ideas?
CheersDavide
On Thursday, January 4, 2024 at 03:42:17 PM GMT+1, Davide Varvello via
Pharo-users 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 a
Hi Davide,
I don’t think something specific to your needs exists, but you can easily build
your own.
There is already for example `haltIfTest` that will halt if you’re in the
dynamic extent of a test.
If you’re dealing with concurrency issues, I don’t understand how the
`haltIfError` is actual
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> wrote:
>
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 escribió:
>
> You can implement another version of TestResult that halts when an error is
> added instead of reco
Hi Gabriel,Your answer leads back to my original question: how can I implement
the "halt on error"? It is not clear to me.
Cheers
Davide
On Monday, January 8, 2024 at 02:31:33 PM GMT+1, Gabriel Cotelli
wrote:
You can implement another version of TestResult that halts when an error is
The Pharo Consortium is very happy to announce that ApptiveGrid GmbH has joined
the Consortium as a Bronze Member.
About
- ApptiveGrid: https://www.apptivegrid.de
- Pharo Consortium: http://consortium.pharo.org
ApptiveGrid is a SaaS tool to digitalize and automatize business pro
