Yes, these do need to be cleaned up and fixed, but they are unrelated to testng->junit4 migration and should be dealt with separately.

<rant>
At least this code asserts something meaningful. There are places where tests assert static string is not null (likely due to mixed parameter order when the tests were originally migrated from junit to testng) and places tests that simply make no sense, like assertNotNull(int) I mentioned yesterday. 
</rant>