Hi Nascif,

> Problem solved - and I tracked it down to how I defined my testcase
> constructor [...]

That was tricky, the JUnit message could have been more explicit. Maybe we
should tell them about this issue, or suggest a patch? Do you know were in
JUnit the assertion error is raised?

I agree with you that the constructor approach may lead too frequently to
this issue, so we will add a setAdapter() as you suggest in release 0.12.
This setAdapter() could be called from within setUp(), we only need it on
a first call to getWindow().
Thank you again for taking the time to investigate this and letting us
know about it.


> Other then that, I am quite happy :-) I ported a few testcases from
> Abbot to UISpec and they not only were cleaner (less code) and faster
> (calls to Thread.sleep() removed) but also more powerful - for example
> ListBox supports the selection of multiple indexes, while in Abbot I
> had to "fake" multiple selection using shift-clicks. Everything worked
> just fine!

That's great news! Please do not hesitate to contact us again if you have
any suggestion for improving UISpec4J.

Thanks,

Régis.