-
-
Notifications
You must be signed in to change notification settings - Fork 519
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
Audit test files for assert/refute with no custom message #386
Comments
exercism/problem-specifications#230 talks about this, Let's open an issue on x-common for any that need them. And for the non-generated ones, l think we could make a check listed note here and do PR's against the list? |
Where they're generated, we can generate the custom message based on the inputs/outputs. The few times that we've had messages in the test data it's just been echoing the inputs, and it hasn't added any value. |
If we can do a good job of it, I say go for it. Writing good error messages can be hard, just about as hard as naming things, and they are more important, because if they are there, they are intended to hold your hand a little bit, and definitely should not misinform. I would rather have a non-informative error message than a misleading one. |
…ogram Remove redundancy from the description of isogram
Currently these files still have this style of test:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'd rather see effort put into created canonical data and converting exercises to using generators than into crafting error messages for non-generated test suites. |
I wonder if @hilary comment will cause the Probot to now leave this open... |
However, the generators should still be generating asserts with sensible failure messages, and we will need to check for this at some point. |
I would far rather see good error messages in the canonical data than generated messages for assert/refute, as I have yet to find generated assert/refute messages useful. If they're doing red/green, they're looking at the tests anyway... but hey, if someone wants to put the effort into adding generated messages for assert/refute, I realize that meaningful error messages in the canonical data is ... unlikely. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This is still relevant |
I think this can be closed now due to #1393 being merged. |
I wonder if that gave some Hacktoberfest credit for this year! |
I doubt it. Also I don't participate in hacktoberfest :) |
I think if anyone got points for it, it would have been Cohen. |
I think that would be a most excellent outcome! |
These should have a custom message put in place as without them you get a very unhelpful message like this:
The text was updated successfully, but these errors were encountered: