Vivek Prahlad is yet another person associated with ThoughtWorks (but seriously, who isn’t these days?) and is the brains behind Frankenstein. The best way to describe it appears to be like Selenium, but for java swing apps. It’s been awhile since I’ve automated thick client stuff, so it wasn’t all the relevant to my circumstance, but here are some takeaways I had which can apply to any automation project.

• Automate things to run as fast as possible, but no faster
• One cool feature of Frankenstein is when there is an assertion failure, it takes screenshot of the entire desktop
• Functional tests contain the intent of what you want to test
• Have a naming convention for worker threads. Then tools like Frankenstein can watch that thread to see if it is finished instead of having timeouts

Direct link is here