On 28 February 2016 at 18:00, Stefan Dösinger stefandoesinger@gmail.com wrote:
The interesting thing is splitting up the output of the big d3d tests in e.g. dlls/d3d9/tests/visual.c into reasonable chunks, preferably matching the functions the tests are in. So that you go from "d3d9/visual is failing" to "d3d9/visual/depth_bounds_test failed, d3d9/visual/test_vshader_input successful".
Ideally this should be stable with regard to changes to the tests. E.g. if 10 lines of code are added at the top of the file it shouldn't break your output processing because the failing ok() lines are in different lines of the file now.
It shouldn't be terribly hard to add a "function" argument to winetest_set_location(), although there may also be something to be said for introducing e.g. a winetest_begin_subtest() function instead.