-
Notifications
You must be signed in to change notification settings - Fork 129
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
Improve fail message when library doesn't exist #2839
Conversation
Previous TB was
|
How it will be
|
In the testing suite is it possible to catch-all any traceback? It would be nice to make sure all expected failures produce a useful message, while a traceback would mean |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it be possible to add some tests for this?
Yeah, that would be nice. @lukaszachy, any simple way to extend the existing test coverage? I quickly tried to reproduce the problem but I end up with the following error instead:
|
Finally reproduced again: repo with fmf root, directory exists as well but the 'main.fmf' of the library node isn't there. |
When adding the test I realized that 'Library @ name' isn't the best way to report the problem.
|
Once teemtee/tests#7 is merged I can/will have to drop the 'ref' from the test. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks for improving this. Just one typo.
When /foo doesn't exist in the fmf root tmt should provide better error than saying `AttributeError: 'NoneType' object has no attribute 'data'`
Test failure irrelevant --> merging. |
When /foo doesn't exist in the fmf root tmt should provide better error than saying
AttributeError: 'NoneType' object has no attribute 'data'
Pull Request Checklist