Re: [lmi] BOOST_TEST needed for automated GUI testing?

[Václav Slavík]

Hi,

On 18 Mar 2014, at 17:45, Greg Chicares <address@hidden> wrote:
> d) Just use LMI_ASSERT() instead of BOOST_TEST(), reasoning that
> the extra work of (c) is not worth the corresponding benefit (and
> that none of the other macros will prove useful for GUI testing).
> 
> I don't remember all the other kinds of tests that will eventually
> be wanted, but we don't need to make a final decision today for
> the one specimen test that's implemented right now--so, in order
> to prevent the problems described below, I'm going to go ahead and
> implement (d) for now.

OK.

> Building with not-yet-committed local changes, I observe this:
> 
>  /opt/lmi/bin[0]$./wx_test.exe --ash_nazg --data_path=/opt/lmi/data
> Everything works as expected.
> 
>  /opt/lmi/bin[0]$./wx_test.exe --mellon --data_path=/opt/lmi/data
> The above "wxWidgets Debug Alert" appears.
> 
> My new hypothesis is that the "Debug Alert" occurs because
> the "about" dialog is automatically displayed at startup in
> the second case. I.e., it's displayed automatically by the
> production system, and therefore by the GUI-test binary too;
> so the GUI-test binary's attempt to display it *again* under
> program control fails (because a modal dialog is already shown,
> blocking menu-command input).

So what should the GUI-test binary do here? I always use —ash_nazg (it’s been a 
few years, but IIRC it wasn’t possible for me and Vadim to run it otherwise?), 
should the test always run in that mode? Or would that be undesirable?

Thanks,
Vaclav