If a robot test imports a library, and that library can't be imported for some reason (not installed, or has a syntax error), robot displays an error on stdout. In addition, the error is mentioned in the robot log before any of the test results, in a section titled "Test Execution Errors". This section appears in the log before the section titled "Test Execution Log".
This sort of error is not available in MetaCI, and it's critical for being able to debug failures that happen in MetaCI due to import errors rather than test failures inside a specific test.
We need to modify MetaCi to detect any of these "pre-test" errors and display them.
If a robot test imports a library, and that library can't be imported for some reason (not installed, or has a syntax error), robot displays an error on stdout. In addition, the error is mentioned in the robot log before any of the test results, in a section titled "Test Execution Errors". This section appears in the log before the section titled "Test Execution Log".
This sort of error is not available in MetaCI, and it's critical for being able to debug failures that happen in MetaCI due to import errors rather than test failures inside a specific test.
We need to modify MetaCi to detect any of these "pre-test" errors and display them.