[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] Automated GUI testing, revisited
From: |
Greg Chicares |
Subject: |
Re: [lmi] Automated GUI testing, revisited |
Date: |
Wed, 12 Nov 2014 02:46:08 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
On 2014-11-12 01:01Z, Boutin, Wendy wrote:
> Greg Chicares wrote:
[...]
>> BTW, we were talking off the mailing list about doing away with the
>> log window and just writing test output to either
>> (1) a flat text file, or
>> (2) stdout or stderr as the case may be.
>> Do you have a preference between those? I'm leaning toward (2).
>
> IIUC, I'd prefer (2) also. It's the same way we capture build results when,
> for example, compiling the system with a command like:
> make install >buildlog 2&>1
> right?
Exactly.
And I envision adding a target to run 'wx_test', which could save
output to timestamped files as we now do with system-test 'md5sums'
files--and, of course, 'md5sum' writes to stdout and stderr.