So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this State. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

Ugh, I wrote tests in a loop style before and it was not allowed.

Ugh, I wrote tests in a loop style before and it was not allowed.

Sorry to hear that. I am OK with it.

FWIW, the reason I asked @chemelnucfin to remove them elsewhere is that the loops introduce a lot of noise, and make debugging failures harder: those tests are "speed bumps" for readers.

I don't have a preference for either style. I can see merits and drawbacks in both.

@tseaver I somewhat agree with you, but the copy-pasta creates other issues.

I am 100% for switching to pytest style, then we can use pytest.mark.parameterize to have one test but multiple data.