-
-
Notifications
You must be signed in to change notification settings - Fork 682
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
Using AssertJ assertions on entire exercises #2147
Comments
This sounds like a good idea, thanks for suggesting! I edited the description with how to contribute to this issue. |
I'm working on this |
Hi, this is my first time, I will be contributing towards open source. May I work on this issue, and migrate some of the tests from junit5 to AssertJ? |
Convert exception assertions to AssertJ in classes starting with 'A' and 'B'. #2156 |
I am working on the Haming |
#2178 is my PR |
#2181 another PR |
Hi, converting markdown from assertEquals to assertThat |
I am in favour of this change, but it does mean that we have to revise the existing policy in POLICIES.md that states that we prefer JUnit assertions over AssertJ. |
Hello @sanderploegsma, I would like to contribute to a few exercises. |
Raised one more PR for few more tests. Please review ! |
Raised one more PR for few more tests. Please review! |
Raised one more PR #2513 which covers all the pending tests which needs to be updated |
I found three more practice exercises to update.
@keszocze I know you're working on Zipper, care to pick up the other two as well? |
edit: Yes of course I can also change those. But there are some more (and I will also change them):
and I sure can also touch them. But that might take until Monday. Btw, in my last PR I was told that the Diffie Hellman exercise was deprecated and that this tells me how to spot that. But looking at the |
I'm guessing you're looking at each exercise's cat config.json | jq -r '.exercises.practice[] | select(.status == "deprecated") | .slug' | sort
|
The test classes use mix of Junit asserts and AssertJ. Since AssertJ assertions are more robust and extensive as compared to Junit5.
Like for example, usage of
assertThatExceptionOfType
from AssertJ is much more readable as compare toassertThrows
from JUnit 5.We can migrate all the asserts from Junit to AsserJ.
Working on this issue
This issue affects several exercises. If you want to contribute to this issue, you don't have to change this in all exercises, feel free to submit small PRs fixing this issue for a single exercise or a small subset of exercises!
The text was updated successfully, but these errors were encountered: