You can use a TestResource for it, and use some sort of memoization.
I don't know if there is a library for memoization in Pharo, but if
the HTTP calls are not that many you can implement it by having a
cache in the test resource, implemented as a dictionary, with the URL
as key and its cached res
That seems to be exactly what I'm looking for. Thanks Peter.
cheers -ben
On Sun, 9 Sep 2018 at 16:11, Peter Uhnak wrote:
> Hi Ben,
>
> take a look at TestResource (its comment and subclasses). It should do
> what you are looking for.
>
> Peter
>
> On Sun, Sep 9, 2018 at 8:08 AM Ben Coman wrote:
Hi Ben,
take a look at TestResource (its comment and subclasses). It should do what
you are looking for.
Peter
On Sun, Sep 9, 2018 at 8:08 AM Ben Coman wrote:
> Say I want to write ten tests for different aspects of a web service point.
> Apart from the risk of relying on an external service,
Say I want to write ten tests for different aspects of a web service point.
Apart from the risk of relying on an external service,
I'd like to poll the web service once rather than ten times.
I wondering about the feasibility of memorizing data between test methods.
Taking for example...
TestC
