-
Notifications
You must be signed in to change notification settings - Fork 27
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
Properly notify desktop entry parsing errors #115
Conversation
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.
Missing tests that check for this exception to be thrown.
This exception is thrown by the |
You can also use a mock object, but the code in here, even if it's "just error handling", needs testing IMO. |
You can also create another issue and postpone that discussion. Let's rather move on. |
Too late, already added the mock AppImage |
I was talking about a mock object, not a mock AppImage. The idea was to test that unit test code, so it should be possible to test this code against a mock object or simply a desktop entry object with broken code. That should be possible in a good software architecture. Adding more and more bloaty AppImages for testing is a bad idea. |
I see, I thought you were talking about a whole AppImage. As I said |
You depict this wrong. There is 5-10 lines of code in this library that you say doesn't have to be tested. It does have to be tested. It's code in here. That's not redundant, it's checking that your "renaming" or whatever works. Doesn't matter if it interacts with another library. As said, there's an option of mocking said library and triggering the the exception block that way, no need to use that library. |
No description provided.