On Wed, 27 Aug 2003, Jakob Eriksson wrote: > I really was looking forward to write a testing application that > runs all the tests.
Yes, that would be very nice indeed. Such a test shell should be something like the JUnit stuff (http://www.junit.org). Here are few things that I'd want in such an app: -- it should be a single executable (.exe preferably) containing all unit tests -- when started, it should go through these steps: * display a dialog explaining what it is and what it would do. The dialog would have OK/Cancel buttons * if OKed to proceed, the program should extract the tests, run them, and collect results, inspect the system. While doing these, it should inform the user what is going on ("Extracting tests...". "Running test X", etc.) The failed tests should be listed below. * when done, it should present the user with 3 buttons: o View Report o Send Report o Cancel * on "Send Report", the report should be emailed to a special mailing list, from where it's later picked up by some scripts and analysed. * We should be able to disable the UI via a command line switch, to allow for automatic execution. > If crosstest was working, the meta-test program could be built as part > of daily wine builds. > Windows testers (myself included) could download the daily crosstest and > automatically upload results into some stats page on winehq. Yes, that would be the idea. With such a setup, we can have a well-known URL (such as http://www.winehq.org/winetests.exe), and you guys can set up fully automated download-test cycles at predetermined intervals. -- Dimi.
