Create some automated widget generation for testing #40
Description
Description:
Bugs like KeyWorksRW/wxUiEditor#1678 are slipping through because we don't have complete coverage of options and in some cases their usage. Currently, all testing is done by manually creating a node for the widget, and then generating the code in all languages and verifying that it compiles in C++ and passes syntax checks in Perl, Python, and Ruby.
The sdi and sdi33 projects are mostly focused on visual aspects -- manually looking at each language's rendition to see if they look the same. No automation is done for these projects, so it does not suffice as complete coverage.
It would be worth investigating whether we can devise a way to do more automatic testing, possibly using AI, that would create a reasonable number of the same controls that use different properties and events which can then be run through the compile/syntax checks. This would probably need to use a separate project file, since it would become quite large and make it awkward to do the visual check above.
In theory, we could write a program that would run a program telling it to display a specific dialog or window, make a screen shot of that window, and then tell the program to exit (could use a timer both in the program being run and the screen capture). We could then run this for each generated language and at the end do a screen capture comparison.