| [data-dev] Deciding on style/library for unit test assertion for the project |
|
There was a pull #33
opened recently to use a different style/library for unit test assertions. Absent any specific direction/standardization from Jakarta on the matter, this is something that should be decided by the developers on this project
who will end up writing and maintaining the tests. Could everyone who has an opinion on the matter either add a thumbs up or thumbs down to the main comment in the pull? Or if you prefer an entirely different approach for testing then add a comment to the
issue. Thanks everyone! Also, on last week’s Jakarta Data meeting, there was some discussion about proposing to reduce the number of meetings for October to 2, but the question was never sent out to the mailing list and therefore
the Jakarta EE calendar still shows that there is a meeting this Wednesday. At this point, it’s too close for making changes, so I’ll plan to start the call this Wednesday at its normally scheduled time. From:
Werner Keil <notifications@xxxxxxxxxx> @keilw requested your review on: #33 Replacing assertion libraries: Hamcrest by AssertJ. — Reply to this email directly, view it on GitHub, or unsubscribe. You
are receiving this because your review was requested. Message ID: <jakartaee/data/pull/33/issue_event/7513815006
ZjQcmQRYFpfptBannerStart
ZjQcmQRYFpfptBannerEnd @keilw
requested your review on: #33 Replacing assertion libraries: Hamcrest by AssertJ. — |