Coverage decreased (-0.07%) when pulling 185a7c33d624d878c6e8daa9da5dfea76e2cbad3 on 1.4/162-remove-auto-assertions-from-tests-names into 2737beb9ec626c96fbbdc04437d50f0aa8a13b4a on release/1.4.
Coverage remained the same when pulling b7e7f91448d1d35e74044c405a8f52c08496e648 on 1.4/162-remove-auto-assertions-from-tests-names into 2737beb9ec626c96fbbdc04437d50f0aa8a13b4a on release/1.4.
Coverage remained the same when pulling 9184a619d9e742b2df02fb823316e2a10b26da04 on 1.4/162-remove-auto-assertions-from-tests-names into 8facb0c04ff9d3fe54a690b22b2ffaae23c7cebf on release/1.4.
Coverage remained the same when pulling 4bb720bfcb4527b42edb4da95cf6063237f07007 on 1.4/162-remove-auto-assertions-from-tests-names into 8facb0c04ff9d3fe54a690b22b2ffaae23c7cebf on release/1.4.
Coverage remained the same when pulling 6467f631fd61c91a044a3390684a383aba6cd1ec on 1.4/162-remove-auto-assertions-from-tests-names into a5a41dbf75954955f065bd1383b0eb62e15b543f on release/1.4.
Sounded like a good idea at the time, but in practicality its pretty useless and confusing.