{"push_id":2429941407,"size":1,"distinct_size":1,"ref":"refs/heads/move-to-junit5","head":"8c32776b2678835594b3c92b1415664bde9b2b10","before":"20a00f08a87737ada893373d702a894d87bda1b3","commits":[{"sha":"8c32776b2678835594b3c92b1415664bde9b2b10","author":{"name":"Artem Prigoda","email":"5b7401b2c24f076b11622d675cf82c234c4783f9@gmail.com"},"message":"Remove expected exceptions from tests\n\nReplace them with AssertJ's `assertThrown`. Modern testing libraries\nseems to favour this approach, because it provides flexibility in\nverifying the cause of the error. For example, JUnit5 doesn't support\nit anymore the `expected` attribute in the `Test` annotation and the\n`ExpectedException` rule. If we ever switch to JUnit5 for testing,\nmigration would be easier.","distinct":true,"url":"https://api.github.com/repos/dropwizard/dropwizard/commits/8c32776b2678835594b3c92b1415664bde9b2b10"}]}
{"actor":{"display_login":"arteam"}}