Beta
only UNChecked Exceptions
Loading description...
Language Features
View
This comment has been reported as {{ abuseKindText }}.
Show
This comment has been hidden. You can view it now .
This comment can not be viewed.
- |
- Reply
- Edit
- View Solution
- Expand 1 Reply Expand {{ comments?.length }} replies
- Collapse
- Spoiler
- Remove
- Remove comment & replies
- Report
{{ fetchSolutionsError }}
-
-
Your rendered github-flavored markdown will appear here.
-
Label this discussion...
-
No Label
Keep the comment unlabeled if none of the below applies.
-
Issue
Use the issue label when reporting problems with the kata.
Be sure to explain the problem clearly and include the steps to reproduce. -
Suggestion
Use the suggestion label if you have feedback on how this kata can be improved.
-
Question
Use the question label if you have questions and/or need help solving the kata.
Don't forget to mention the language you're using, and mark as having spoiler if you include your solution.
-
No Label
- Cancel
Commenting is not allowed on this discussion
You cannot view this solution
There is no solution to show
Please sign in or sign up to leave a comment.
This is a duplicate of https://www.codewars.com/kata/5595c56aa6ca910f27000155
You even submitted an exact same solution as this kata in that kata. May I ask you what is the point of creating this kata in the first place?
The initial code and sample tests are testing a completely different thing from the actual tests (
callMe
instead ofdoThrow
). What is actually being tested here?There should also be a
RuntimeException
provided as a test case; there are no reasons not to provide one.I'd suggest:
void callMe()
method with a more generic one, likevoid doThrow(Exception e)
method from sample code to make it a bit more puzzling.