What facilities are available in nim for automated testing of a GU interface - particularly for an app using oldwinapi or winim?
Some savants advise unit testing on the non GUI parts - okay, but that misses the point. What would be nice is a facility which can alternately log out an actual window structure to a text log file or read in a previously logged file and compare it with that structure. This should be interspersed with "robot" commands to exercise the GUI. That way a human can manually run through a test by hand just once (logging out the results) and then thereafter do automated regression testing against the log file. Granted that os handles are subject to change between executions - but they could be replaced by order-of-appearance symbols in the log output - e.g. #1, #2, #3, etc. Something like this should be possible - using win32 EnumerateWindows & FindWindow etc. But I would hate to reinvent the wheel.
