On Sun, Mar 28, 2010 at 12:53 PM, Seth Shelnutt shelnutt2@gmail.com wrote:
Alright after creating a few test scripts and playing around with things I think I have finally settled on exactly what my proposal is. It is in three parts,
- Convert wpkg (or appDeploy) scripts into ahk scripts. I believe that I
can convert a hundred or so without to much work.
- I'd like to implement a more aggressive error reporting. I want to have
appinstall rerun failed test using WINEDEBUG=+all (or possibly have it guess what channel is needed to be watched). Saving the output of this will allow one to more easily debug the program. You won't have to go back and rerun the program yourself in wine, you will already be given the output so you can see what failed, where.
- I'd also like to implement a feature to have the output more in the
format of test.winehq.org. I am thinking that it would be easier to have it done split into two scripts, one on client-side, one server-side. Have the client format all the information into an xml file, and then server-side convert that xml into something along the lines of what test.winehq.org looks like.
I can go more in depth with each step I'd like to take, but I am not sure how specific I should be with my proposal? I was looking at last year's proposals and they didn't seem overly in depth on the steps they planned to take.
The five sample scripts and the edited appinstall.sh can be found here, http://shelnutt2.host56.com/appinstall/ . I've found the easiest way to add the scripts is to copy them into the ~/.appinstallcache folder after it's created and before the tests are run.
You'll want to make a formal proposal on http://socghop.appspot.com/gsoc/.
One other thing you may want to aim for is better windows support. It should be possible to run appinstall in windows under cygwin (it should be pretty easy to fix, actually).