GSoC Idea: Tools - Winetest Scripting Interface

[Zhenbo Li]

Hello,
These days, I'm discussing this idea in mesa-piglit group[1], and I've
finished a proof-of-concept script, showing that it is possible to run
wine's test suite from piglit (mesa's test suit)[2]

In piglit's mail list, I said that subprocess is necessary and it
could be a waste of time. After sending that mail, I realized that we
can redirect stdout and stderr to files, and then analyze the
results[3] instead of using subprocess[4]. With os.system, we spent
8.617s on the tests for riched20, while the bash script[5] needs
0m8.497s.

IMHO, this project should provide a convenient interface for both
piglit and human developers. Do you have any ideas that which function
this script should provide?

Thank you

[1]: http://comments.gmane.org/gmane.comp.video.piglit/17480
[2]: https://github.com/Endle/piglit-gsoc/tree/mesa_wine
      https://github.com/Endle/wine-gsoc/tree/mesa_wine
[3]: https://gist.github.com/Endle/299dcb44ea463c05e6fb
[4]: https://gist.github.com/Endle/4667c6c867a9c4981312
[5]: https://gist.github.com/Endle/ba88c2b5bfec6b14a73e

2016-02-14 19:04 GMT+08:00 André Hentschel <nerv at dawncrow.de>:
> Am 14.02.2016 um 02:39 schrieb Zhenbo Li:
>> When it comes to the schedule, I think "Winetest Graphical User Interface" might be a choice to provide enough work for this summer. I guess there are some coupled jobs for these two ideas.
>>
>
> That's actually a good point, IIRC getting the output simultaneous into the result file and also into the parser for the GUI was a tricky part.
>
>



-- 
Have a nice day!
Zhenbo Li