Le 03/02/2014 21:41, Usman Bhatti a écrit :
On Sun, Feb 2, 2014 at 2:43 PM, Marcus Denker <[email protected]
<mailto:[email protected]>> wrote:
On 02 Feb 2014, at 14:31, [email protected]
<mailto:[email protected]> wrote:
> For diligence and curiosity leading up to the Pharo3 release, I
downloaded build image 30733 (with PharoLauncher)
Getting an image green is a lot of little, trivial, hard work… and
green always means “Green in this context”. Just headless vs.
non-headless
changes a lot, for example.
Another wonderful thing is that tests are fine when run
individually, but fail when running all tests.
We need to think about automatic UI testing…
It will be awesome to have automatic UI tests.
Well, it can be done as it is now.
It's fairly easy in Pharo to write tests that open a GUI, test a few
things in it, and close it. There, you can already test automatically
that your gui updates correctly when the model change.
It may be a bit harder to trigger events on specific positions, but not
that much difficult. A way to write a test method out of Sean event
recorder would be nice there.
Currently, I can go as far as invoking the UI but then to complete the
fields in another process/thread, I haven't really spent enough time. I
think that's already discussed on the mailing list but some time I
should have a look. Automated tests before a release/roll-out will be a
dream coming true ;-).
Yes. Especially on all the gui parts: drag and drop for example.
But, technically, we're not very far. It's just that nobody writes tests
that way.
Thierry
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
