Martin wrote:
Regarding your script interface, I think it should accept these parameters:
* GIT_ID_1 - bisection start
* GIT_ID_2 - bisection end
Sure, and/or dates and/or releases.
* PNGs - list of PNG files which describe bug hit cases;
No. The script should not invoke autohotkey, either.
Mikolaj Zalewski wrote:
I now start to understand the structure of the tests. Do you know if
there is a known regression in current Wine that I could use to try to
do some scripting? If not I could use wine-0.9.43 as a reference with
it's Win16 regression that affects the pptviewer and
Hi Mikolaj,
nice work!
I saw that you successfully ran cxtest.sh script on your machine and
submitted results. Currently, we are in process of setuping cxtest.sh
(tests Wine make test, Picasa, WinZip, WordViewer, ExcelViewer, PptViewer)
and 3dMark2000 tests nightly on our testing machines. Once
Currently I'm trying to learn how cxtest works. But it looks like a
good idea to find sources of such regressions. I could help to write
such a script. I will check how my script fits into it.
Mikolaj Zalewski
Completely awesome, thank you!
Mikolaj Zalewski wrote:
I wrote a small script that automates regression testing. It requires
an Autohotkey script that tests the program and creates a file
C:\Test-failed.txt if the test failed. The bash script will then do
the regression testing. It starts
Hi Mikolaj,
see winebot - a console Wine package tool for Windows programs for how
to automate AutoHotkey installation for given wineprefix.
http://winebot.sandbox.cz
Regards
Vit
Mikolaj Zalewski wrote:
I wrote a small script that automates regression testing. It requires
an Autohotkey
