On Fr, 2007-08-10 at 12:15 +0200, Paul Vriens wrote:
I just want to get people's opinion(s) about the needs/requirements/whishes for both the conformance tests themselves (including winetest) as well as the webpages.
* Please make the links "Previous build" / "Next build" working!
* I really like to Filter the Results by DLL: - Try to find the Test-Result, when a new Failure popped up in a specific Windows Version. (Current Example is oleauth32/vartest for w2k)
- Try to find the most recently Results for a Test. (For Example, when a new Test was added) Find this for a specific Windows Version.
* http://bugs.winehq.org/show_bug.cgi?id=3187
* Can we add the selected locale to the results? (Example issue are the current failures in oleauth32/vartest)
* Can we add the tested dll-version to the results? (This is a shortcut for the installed versions of: IE, msi, DirectX, ...)
* winetest.exe: Allow "/?" as an alias for "-h" * winetest.exe: Allow other character in the TAG (underscore as example) * winetest.exe: Enable the "Stop" button * winetest.exe: make the progress-bars the same size * winetest.exe: Be more verbose during extract / test / upload (add "x of y" somewhere; add used time somewhere)
Can we optional collect the results with a tempfile to replace the Pipe? (set WINETEST_OUTPUT to the Filename as Example)
This will make it possible with an updated wine/test.h to add win16 tests in the testsuite.
I do not expect to run winetest on win3.x, but just prevent the 16Bit API to fail.