-----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. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJW5cYnAAoJEN0/YqbEcdMwlmsP/ixkVLKKsoTECstUx0Zgl8yr aoTqIN/jCQlfChAX9/SzK8ZS3Qa+MNjnG2XDKRt5Hqmhs5kxsszs0yFWB9RrR8AA DpaJGvVzQwCC0DUBxNli9roJHsJ/zfURQ3+5ktee+yZMpBXBt1/UzbXeujoOPeWX O6ctHvMTOAK2124pzZVeLEq+Xb1UNy7B+Qbp/zYt0MEuen6EfYAqUmb4hCGM2Iac zaf+k0XoJidNbY56y3jU7hVPaIQG2s+6BTMO1mWJZ3ADkU0gihAAFfvFSGrllbRs 4oAyuUU5klMjaPWTOjGwXn1aIMBAx0F8WRTdanK8WjEzYEGFGWa3+ZxmPZh1AMGU RYrcE+EfUsCyBgQZE3kOoqJmeB/EIHchu4szhIyT+WgrHn8RBFPJyozaHisuJjBd SdCb12yzwtElSTGrWxyJ3FpArRoKjb6MT2caFPw5dKM+01hY1Ssa+es3NEXWf2NL ZdItjfhqBjfpn99awwRP8ZooK443twiuvdVrF1qznS49Br3n67xHjki5zIm66qcw sPnqU1+EKpskXmrXZ5Su/bMCUExDNZyyXtb4EZvOOGYf0ifDPpdQ2mEmWQeGCtZ4 +Z+ZzovxBj1prl5hQl3vy/MAoEJj1tfsCUklbCEmzw1helSwVpxlkwFDyz0agNoR p8+EU7a8CXkwasps5NPP =Ee+E -----END PGP SIGNATURE-----