update tests to extend UnitTest

[dev-mlb]

No description provided.

[drivenflywheel]

I've got no problem with updating each of these to extend UnitTest, but I thought (think?) we've only seen impact to other tests if the "non-UnitTest" test classes invoke code that leverages ConfigUtil. Is that not the case?

[dev-mlb]

I've got no problem with updating each of these to extend UnitTest, but I thought (think?) we've only seen impact to other tests if the "non-UnitTest" test classes invoke code that leverages ConfigUtil. Is that not the case?

Yep, that is true. I felt that I was in here anyways and should just have the tests extend UnitTest, hopefully, to future-proof it. Hopefully JUnit implements the @BeforeSuite/@AfterSuite, or what ever they end up calling it, and the need for this could probably go away. But the issues (456) has been open since 2016, so there's that.