Towards leveraging app build and unit tests as a way to test wine

[Nicklas Börjesson]

> The name's not that important,though, tbh...
In my experience, good names and structures are really important, since stuff like this inevitably grows. 
And confused newbies needs more explanations than necessary. And other people gets confused too. :-)

Anyway, something like this, perhaps?  
winetest_app_gui - The current appinstall, tests only the finished applications through their GUI.
winetest_app_build - Testing the actual building of applications.
winetest_app_suite - Running applications own test suites(even if they are GUI tests)

I would like to separate _build and _suite to clean up and because _build is optional. _suite could(and probably should) be also run on officially released binaries.

Why not just run _app_suite tests under _app_gui? Two reasons:
* Because _app_suite probably need lots of pretty advance test suite-related tools to be installed. I would like winetest_app_gui to be as clean as possible, so that it's really simple (and problem-free) to run.
* I think that _app_suite (and certainly _app_build) probably only gets run by very experienced "winos" like Dan. 
If somebody just has an available VM somewhere(like) and like to help out, _app_gui makes this possible. _app_gui is also a little more about CPU than build environments, which should be a but easier.

This is all IMHO, of course.

//Nicklas