I and a collegue of mine have been looking at gui testing systems. All solutions have it's pro's and con's, but I couldn't find a real suitable solution for me.
I need the gui testing for nyx, which depends on swing and swt (swt is a work in progress thougb, which currently breaks nyx completely).
My goal with gui testing is to also test things that are under the covers in eg swing. I want to to know what messages are fired and how many times they are fired and test for execution paths. Also just testing a single component / widget is a tedious task, so eg testing a JComboBox and an swt Combo, you have to add a window surrounding it, which should be automated.
I am thinking of filling the gap myself and write a junit extension for nyx, swing and swt.
Jemmy looks good, but also seems limiting (you can play scenario's, but eg not record them). You also need jelly (is not the jakarta jelly!) to make testcases out of them.
If anyone has some good or cool scnerios I can use for swing and swt testing, please let me know and if you'r interested help me out. Let me see the light :)
For now my conclusion is that gui testing is way too bad to be usefull and not very timesaving, especially when there is a fast rate of changing the gui itself.