Re: [lmi] Automated GUI testing, revisited

[Greg Chicares]

On 2014-11-09 01:21Z, Greg Chicares wrote:
> 
> 00:37:10:     validate_output_illustration: ERROR (Assertion failure: 
> Expected wxDialog dialog was not shown. [file 
> /opt/lmi/local/include/wx-3.1/wx/testing.h, line 315, in ReportFailure()].)
> 00:37:11:     validate_output_mec: ERROR (Assertion failure: A message box 
> "Sorry, could not open this file." was shown unexpectedly, expected wxDialog. 
> [file /opt/lmi/local/include/wx-3.1/wx/testing.h, line 315, in 
> ReportFailure()].)

Why would these tests fail? As for the second one, I'm running
  $./wx_test.exe --ash_nazg --data_path=/opt/lmi/data
which certainly has the power to create and handle '.mec' files.
Should the diagnostic name the file that it couldn't open?
Is the use of
  configurable_settings::instance().default_input_filename()
a possible cause? (I see no new files written in /etc/ though.)
I'm not sure which of these two assertions
    unnamed_output.assert_exists();
    existing_output.assert_exists();
is failing; if it's the latter, then am I again missing a
required file?

The 'validate_output_illustration' test seems to fail in a
different way. Is the explanation that I once again don't have
some required file, and that the test just reports that
precondition failure in a different way?

If this and other failures are due to missing files, then would
it make sense to test for their existence first, not through any
GUI operation but instead with something like access(2)?