https://martinfowler.com/bliki/UnitTest.html
Martin Fowler
Although I start with the notion of the unit being a class, I often take a bunch of closely related classes and treat them as a single unit.
https://medium.com/@_ericelliott/i-use-the-well-known-defini...
Kent Beck
Unit tests test individual units (modules, functions, classes) in isolation from the rest of the program
Such great evidence.
Then, he goes on to, and let me emphasize this, defend the criticism that other people make that this type of test is not a unit test. (sound familiar?):
Indeed using sociable unit tests was one of the reasons we were criticized for our use of the term "unit testing". I think that the term "unit testing" is appropriate because these tests are tests of the behavior of a single unit. We write the tests assuming everything other than that unit is working correctly.
I'm not sure how thoroughly you're looking to be refuted here but I feel I can't quite do a better job.
It is perfectly fine to test multiple classes as a unit, in fact you probably already do so, as I would be extremely surprised if you mock your string class in all your unit tests.