-
Notifications
You must be signed in to change notification settings - Fork 566
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
Use Hamcrest assertions instead of JUnit #1749
Comments
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Sep 14, 2022
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Sep 15, 2022
romain-grecourt
pushed a commit
that referenced
this issue
Sep 15, 2022
romain-grecourt
pushed a commit
that referenced
this issue
Sep 15, 2022
Two items have been fixed in helidon-3.x, and will need to be backported in 2.x: |
@romain-grecourt Can any contributor (not a member of helidon) do backport? I can try to do it. Are there any instructions for backport process in the documentation? |
You can do a backport. There is no special process at the moment (though we've been working on one recently). A |
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Sep 16, 2022
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Sep 16, 2022
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Sep 17, 2022
1 task
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Sep 21, 2022
…di/reference-counted-context (helidon-io#1749)
1 task
romain-grecourt
pushed a commit
that referenced
this issue
Sep 23, 2022
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Sep 23, 2022
…di/reference-counted-context - backport 2.x (helidon-io#1749)
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Sep 23, 2022
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Apr 18, 2023
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Apr 18, 2023
romain-grecourt
pushed a commit
that referenced
this issue
Apr 19, 2023
romain-grecourt
pushed a commit
that referenced
this issue
Apr 19, 2023
romain-grecourt
pushed a commit
to Captain1653/helidon
that referenced
this issue
Apr 21, 2023
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Apr 21, 2023
romain-grecourt
pushed a commit
to Captain1653/helidon
that referenced
this issue
Jun 5, 2023
romain-grecourt
pushed a commit
to Captain1653/helidon
that referenced
this issue
Jun 5, 2023
romain-grecourt
pushed a commit
to Captain1653/helidon
that referenced
this issue
Jun 5, 2023
romain-grecourt
pushed a commit
to Captain1653/helidon
that referenced
this issue
Jun 5, 2023
tomas-langer
added
help wanted
Extra attention is needed
testing
3.x
Issues for 3.x version branch
4.x
Version 4.x
labels
Sep 7, 2023
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Jun 13, 2024
barchetta
pushed a commit
that referenced
this issue
Jun 26, 2024
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Jun 26, 2024
romain-grecourt
pushed a commit
that referenced
this issue
Jul 1, 2024
Captain1653
added a commit
to Captain1653/helidon
that referenced
this issue
Jul 2, 2024
romain-grecourt
pushed a commit
that referenced
this issue
Jul 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment Details
Problem Description
Currently we have a few tests that still use JUnit assertions, such as
assertEquals(actual, expected, "Test a and b are equal")
all of these should be replaced with Hamcrest, such as:
assertThat("Test a and b are equal", actual, is(expected))
)There are a few assertions we can use:
fail("")
assertAll()
assertThrows
The text was updated successfully, but these errors were encountered: