Remove print lines in tests

I think integrating `examples` directories for both the libraries here could be a better place for these print statements. In general, unit tests don't need to have a ton of print statements if they succeed, and their error message should they fail should be enough to diagnose the issue.

We've been mixing up unit tests with integration tests, and adding print statement to that whole mix for a long time, but a little cleanup there would not be a bad thing IMO. Thoughts?

Start by inventorying print statements across the unit and integration tests, then identify which tests are intended to remain unit tests and which belong in the libraries' examples directories. Done means unnecessary output is removed from successful unit-test runs and failures still provide sufficient diagnostic information.

Written by the indexing model from the issue text.