I have been writing some acceptance tests for a Flex application in Selenium using Nose, and VirtualBox. To do so, I had to fix quite a few bugs in the Selenium Flex API. Are all Flex devs over-engineers? The SFAPI had a scary series of interacting methods, a helper class, multiple pieces of shared state mutated by what appeared to be simple query methods, and two entirely different ways of handling two objects which have the same formal interface, all of which was just to walk a tree of nodes (at least, as far as I could see).
I spent ...
