Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Robot import errors aren't being reported #464

Open
boakley opened this issue Aug 2, 2019 · 1 comment
Open

Robot import errors aren't being reported #464

boakley opened this issue Aug 2, 2019 · 1 comment
Labels

Comments

@boakley
Copy link
Contributor

boakley commented Aug 2, 2019

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.

@boakley
Copy link
Contributor Author

boakley commented Sep 11, 2019

I've attached an output.xml file which shows one of these types of errors. It was generated by this simple test case:

*** Settings ***
Library  bogus

*** Test Cases ***
Whatever
    log  whatever!

(I had to give the file a .txt suffix; github wouldn't let me attach .xml oddly enough)

output.xml.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant