1. Deployment projects
  2. Deploy Trunk Nightly
  3. Releases

Release: openmrs-trunk-2299

INCOMPLETE
Deploys nightly Demo and publishes nightly to sourceforge

Commits

Comparison is available only for releases created from the same branch as this release.

This release
Author Commit Message Commit date
teleivo <teleivo@users.noreply.github.com> teleivo <teleivo@users.noreply.github.com> b8cfe58bf282fd24b2906322fb56c0083576e070 Assert collections are empty using hamcrest
which in case the collection is not empty gives us

java.lang.AssertionError:
Expected: is an empty collection
     but: <[a]>

knowing whats in it might already give you a clue as to what went wrong
teleivo <teleivo@users.noreply.github.com> teleivo <teleivo@users.noreply.github.com> f4879ac62b4536e604d6980107ee0dd2c8cc0254 Use hasSize assertion for collections
So in case the size is not equal to one I do not only get an error
message saying you wanted the expression to be true but it was false.
Instead I want to see the actual size of the collection in this case
teleivo <teleivo@users.noreply.github.com> teleivo <teleivo@users.noreply.github.com> e9005fd8764e8e6dfa2e66ecd11bf786f83ae4a5 Use assertTrue instead of assertEquals(true, expression)
since assertTrue/assertFalse are specifically written for these assertions
achilep <you@example.com> achilep <you@example.com> 41665fd864c6b43af841d4199bfd889ab9a3faa3 TRUNK-5816: Migrate api package tests to Junit 5
teleivo <teleivo@users.noreply.github.com> teleivo <teleivo@users.noreply.github.com> 99a8057e52a899169d2a731111217eea11cff5a7 Use assertThrows instead of try/catch in tests
this idiom seems to stem from the JUnit 3 times
https://github.com/junit-team/junit4/wiki/Exception-testing#trycatch-idiom
now with JUnit 4/5 the preferred approach is assertThrows
https://github.com/junit-team/junit4/wiki/Exception-testing#using-assertthrows-method
teleivo <teleivo@users.noreply.github.com> teleivo <teleivo@users.noreply.github.com> da4854a7a671d3add241e87787e4563953c3396e Use assertFalse instead of assertEquals(true, expression)
since assertTrue/assertFalse are specifically written for these assertions
?ukasz D?bicki <sacull@gmail.com> ?ukasz D?bicki <sacull@gmail.com> 956dd38f63a7ea92bba644b2bb8b8d16ba91e3d1 TRUNK-5858: Change of object type to primitive (#3347)
?ukasz D?bicki <sacull@gmail.com> ?ukasz D?bicki <sacull@gmail.com> cfab0a158fa26e8fe72b8ee78ec979f3bd35fb1e TRUNK-5860: Change of object type to primitive (#3346)
teleivo <teleivo@users.noreply.github.com> teleivo <teleivo@users.noreply.github.com> 315db7334f47b2a5737271eb0733690f521ee2c8 Use assertTrue instead of assertEquals(true, expression)
since assertTrue/assertFalse are specifically written for these assertions
achilep <you@example.com> achilep <you@example.com> 46360a939d90d991d452e6a42479e060d73a7f82 TRUNK-5816: Migrate unit tests to Junit5 3
achilep <you@example.com> achilep <you@example.com> e02183887a9e503d79794873f838d89848db0869 TRUNK-5816: Migrate unit tests to Junit5
achilep <you@example.com> achilep <you@example.com> 39f9059f2f7cdd57260de8393cb50dbc04631ed9 TRUNK-5816: Migrate unit tests to Junit5 1
achilep <you@example.com> achilep <you@example.com> 0f87146c751519429d4734ff722eff1ee1197101 TRUNK-5816: Migrate unit tests to Junit5 2