GSoC Idea: Tools - Winetest Scripting Interface

[Sebastian Lackner]

On 12.02.2016 16:18, Zhenbo Li wrote:
> Hello, I'm Zhenbo Li. I participated in GSoC twice. This year, I want
> to work on "Tools - Winetest Scripting Interface". After "make test",
> checking the output in stdout manually is horrible. As ok() macro is
> used quite widely, my patches should cause no surprise. That is to
> say, other developers need to read neither my patches nor the
> changelog to continue their jobs, although ok() macro and other tools
> for test have been changed.
> 
> I think there will be two steps for the goal:
> 
> 1. ok() macro
> =====================
> 

[...]

> 2. compare the results
> =======================

[...]

Thanks for the proposal. Not sure if its just my feeling, but so far the
task list doesn't sound like it will provide enough work for several weeks.
Goal 1 for example could be done in a few hours, if such a design is acceptable.
Code snippets to create diff files is also publicly available, so comparing
test failures could turn out as simple as calling one library function.
Not sure if Stefan Dösinger had any additional ideas in mind (adding him as CC),
but I personally think a few extra challenges would not hurt. ;) If you have
any additional ideas, you are of course also welcome to add them.

Regards,
Sebastian