Testing a callback (no fuctional test)

> Hi,
>  It's not really clear to me how to test a callback without interact with a
> browser or tool like selenium, watir etc. etc
>
> Let's take an example from the Seaside book:
>
> AnchorCallbackExample>>renderContentOn: html
>  html text: count.
>  html break.
>  html anchor
>  callback: [ self anchorClicked ];
>  with: 'click to increment'
>
> How can I trigger the callback via unit test?

>
> Lukas Renggli wrote
>>
>> +1 for Philippe's answer.
>>
>> You do not want to test the Seaside callback mechanism, do you? This is
>> already tested in functional and unit tests.
>>
>> Lukas
>>
>
> I see. The reason behind my thoughts is I'd like to reduce feedback of the
> correctness of my code without waiting for an interaction with a browser or
> a functional test.
>
> Let's take another simple example from your book:
>
> WebCounter>>renderContentOn: html
> html heading: count.
> html anchor
> callback: [ self increase ];
> with: '++'.
> ....
>
> And let's suppose I already tested "increase" and "decrease".
> Unfortunately by mistake, I change the code this way:
>
> WebCounter>>renderContentOn: html
> html heading: count.
> html anchor
> callback: [ self decrease ];
> with: '++'.
> ....
>
> I cannot realize the error until I run some functional tests. That's why I
> prefer to have a warning of my mistakes early in my development flow.