If I understand how this works, there is a clear use case for using this over say Selinium: flash interaction testing. so assuming you have a fixed dimension site in the fluid browse, you could interact with flash widgets... Right? or am I totally off track here?
For most other functional testing I'd stick to webrat that I can bake into my build script.
But flash testing...I really want to crack that nut.
We're using it, and it's the only solution we've found that works well for Flash testing. Costs a bundle, but was worth it to automate our (mostly Flash-based) app...
Also, it doesn't look like Fake would be able to interact with Flash/Flex apps, based on the screenshots. Looks like DOM scripting to me.
I'm not sure I follow you? This app doesn't have any ability to "record" (especially not click coordinates). Rather, you assemble your actions by drag-and-drop only. Selinium is far more full featured browser automator. However, this power comes at the cost of simplicity. Selinium is broken up in to three separate components that must be installed and work together in order to function. This isn't a bad thing. It's just far more complicated than Fake.
For most other functional testing I'd stick to webrat that I can bake into my build script.
But flash testing...I really want to crack that nut.