On Wed, Mar 09, 2005 at 12:03:01AM +0800, Dmitry Timoshkov wrote:
Hello,
it appears that new test for a visible desktop works fine, time to make running tests on a visible desktop a mandatory requirement.
Will this not mean no winrash tests any more, only manual ones?
I haven't got around to reprogram winrash yet, you know...
"Jakov af Wallby" jakov@vmlinux.org wrote:
Will this not mean no winrash tests any more, only manual ones?
I haven't got around to reprogram winrash yet, you know...
I know nothing about winrash, but if it's possible to tell it to run the tests on a visible desktop then it would be great.
On Wed, Mar 09, 2005 at 09:04:20AM +0800, Dmitry Timoshkov wrote:
I know nothing about winrash, but if it's possible to tell it to run the tests on a visible desktop then it would be great.
Not as far as we know. I still don't understand why you insist on killing winrash and automated testing along the way.
Please fix winrash if it can be fixed, if not just find a way to sort/fiter/etc the tests better based on the visibility flag, don't prevent the ones that work from working.
Dimitrie O. Paun wrote:
On Wed, Mar 09, 2005 at 09:04:20AM +0800, Dmitry Timoshkov wrote:
I know nothing about winrash, but if it's possible to tell it to run the tests on a visible desktop then it would be great.
Not as far as we know. I still don't understand why you insist on killing winrash and automated testing along the way.
Please fix winrash if it can be fixed, if not just find a way to sort/fiter/etc the tests better based on the visibility flag, don't prevent the ones that work from working.
+ 1
/Jakob
On Wed, 2005-03-09 at 06:52, Dimitrie O. Paun wrote:
On Wed, Mar 09, 2005 at 09:04:20AM +0800, Dmitry Timoshkov wrote:
I know nothing about winrash, but if it's possible to tell it to run the tests on a visible desktop then it would be great.
Not as far as we know. I still don't understand why you insist on killing winrash and automated testing along the way.
Please fix winrash if it can be fixed, if not just find a way to sort/fiter/etc the tests better based on the visibility flag, don't prevent the ones that work from working.
The patch is already committed so we have to see how many tests do come in now.
Couldn't a quick-and-dirty one be to let winrash fill one of the RunOnce keys? That way we have a semi-automated testing environment, at least if the user logs in.
Paul.
Paul Vriens wrote:
On Wed, 2005-03-09 at 06:52, Dimitrie O. Paun wrote:
On Wed, Mar 09, 2005 at 09:04:20AM +0800, Dmitry Timoshkov wrote:
I know nothing about winrash, but if it's possible to tell it to run the tests on a visible desktop then it would be great.
Not as far as we know. I still don't understand why you insist on killing winrash and automated testing along the way.
Please fix winrash if it can be fixed, if not just find a way to sort/fiter/etc the tests better based on the visibility flag, don't prevent the ones that work from working.
The patch is already committed so we have to see how many tests do come in now.
Couldn't a quick-and-dirty one be to let winrash fill one of the RunOnce keys? That way we have a semi-automated testing environment, at least if the user logs in.
AFAIK that's the only way of making winrash run the tests on a visible desktop.
regards, Jakob
"Dimitrie O. Paun" dpaun@rogers.com wrote:
Not as far as we know. I still don't understand why you insist on killing winrash and automated testing along the way.
Please fix winrash if it can be fixed, if not just find a way to sort/fiter/etc the tests better based on the visibility flag, don't prevent the ones that work from working.
I don't see why the tests should be filtered, and how you are going to maintain new not yet existing tests. We really want to see all test results or nothing.
The patch didn't target winrash at all, the purpose of the change was to make the tests represent a usual Windows environment which vast majority of applications expect to see. The change was approved Alexandre.
I'm not going to fix winrash, it's not a part of the Wine tree.
Dmitry Timoshkov wrote:
"Dimitrie O. Paun" dpaun@rogers.com wrote:
Not as far as we know. I still don't understand why you insist on killing winrash and automated testing along the way.
Please fix winrash if it can be fixed, if not just find a way to sort/fiter/etc the tests better based on the visibility flag, don't prevent the ones that work from working.
I don't see why the tests should be filtered, and how you are going to maintain new not yet existing tests. We really want to see all test results or nothing.
The patch didn't target winrash at all, the purpose of the change was to make the tests represent a usual Windows environment which vast majority of applications expect to see. The change was approved Alexandre.
I'm not going to fix winrash, it's not a part of the Wine tree.
I can submit winrash to wine-patches, maybe that will speed things up?
regards, Jakob
Jakob Eriksson wrote:
Dmitry Timoshkov wrote:
"Dimitrie O. Paun" dpaun@rogers.com wrote:
Not as far as we know. I still don't understand why you insist on killing winrash and automated testing along the way.
Please fix winrash if it can be fixed, if not just find a way to sort/fiter/etc the tests better based on the visibility flag, don't prevent the ones that work from working.
I don't see why the tests should be filtered, and how you are going to maintain new not yet existing tests. We really want to see all test results or nothing.
The patch didn't target winrash at all, the purpose of the change was to make the tests represent a usual Windows environment which vast majority of applications expect to see. The change was approved Alexandre.
I'm not going to fix winrash, it's not a part of the Wine tree.
I can submit winrash to wine-patches, maybe that will speed things up?
Probably, but all you need to do, AFAIK, is to create the service with the SERVICE_INTERACTIVE_PROCESS flag set. That should make all windows display on an interactive (and hence visible) desktop and window station.
Rob
Jakob Eriksson wrote:
Dmitry Timoshkov wrote:
"Dimitrie O. Paun" dpaun@rogers.com wrote:
[snip]
The patch didn't target winrash at all, the purpose of the change was to make the tests represent a usual Windows environment which vast majority of applications expect to see. The change was approved Alexandre.
I'm not going to fix winrash, it's not a part of the Wine tree.
I can submit winrash to wine-patches, maybe that will speed things up?
I would like to see it put in.
--
Tony Lambregts
-
Dimitrie O. Paun -
Dmitry Timoshkov -
Jakob Eriksson -
jakov＠vmlinux.org
-
Paul Vriens -
Robert Shearman -
Tony Lambregts