GSoC Idea: Winetest Graphical User Interface

Sun Mar 13 14:57:27 CDT 2016

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Am 2016-03-13 um 05:08 schrieb Zhenbo Li:
> 1. Choose which dlls to be tested. Users could use GUI, CLI, or a
> config file. 2. Show the result in winetest, or render it to html 
> 3. Allow to leave tag and email blank if the user doesn't want to 
> submit the result to test.winehq.org, and they can fill them when 
> submitting them.
What are the use cases for this? A gsoc proposal is a lot more
convincing if you can name some scenarios how it will help Wine users,
wine development or other projects around Wine.

My main concern is that in the past all projects around a winetest gui
didn't really succeed because there's no clear use for a better
winetest gui. For me as a developer "make test" is good enough, and we
already have more test (failure-) reports on test.winehq.org than we
can make productive use of.