[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:39:56 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
On 2014-11-11 23:46Z, Boutin, Wendy wrote:
[...]
> 22:40:26: FAILURE: 5 out of 24 tests failed.
Good to know--maybe I'll be able to get more tests to pass,
though I haven't yet. But right now I really only want to
ask about this:
> 22:40:13: configurable_settings: ERROR (Assertion
> '(settings.xsl_fo_command()) == ("CMD /c c:/fop-0.20.5/fop")' failed
> (expected CMD /c c:/fop-0.20.5/fop vs observed CMD /c /fop-0.20.5/fop). [file
> /opt/lmi/src/lmi/wx_test_config_settings.cpp, line 41] )
The difference is the msw "C:" drive letter:
expected CMD /c c:/fop-0.20.5/fop
observed CMD /c /fop-0.20.5/fop
IIRC, some end users in field offices install to a drive other
than "C:". How can the "expected" command work for them? If
they install to, say, "E:", then do we give them a variant
configuration file that specifies "F:/fop-0.20.5/fop"?
Also IIRC, Vadim deliberately has no "C:" drive. And I sometimes
run archived lmi versions from "F:", and "File | Print preview"
works in that case, though I have fop on "C:". My configuration
file says
<xsl_fo_command>CMD /c /opt/lmi/third_party/fop-0.20.5/fop</xsl_fo_command>
without any drive letter...so I don't see why we need one. But
the only way to be sure is to test a field-distribution CD.
- Re: [lmi] census benchmark test (was: Automated GUI testing, revisited), (continued)
Re: [lmi] Automated GUI testing, revisited, Vadim Zeitlin, 2014/11/14
Re: [lmi] Automated GUI testing, revisited, Greg Chicares, 2014/11/12
Re: [lmi] Automated GUI testing, revisited, Greg Chicares, 2014/11/12
Re: [lmi] Automated GUI testing, revisited, Boutin, Wendy, 2014/11/11
Re: [lmi] Automated GUI testing, revisited, Boutin, Wendy, 2014/11/11