Unit tests for the str() method have also been added.
Previously, a separate test only helper function was being used by the
test matchers which has regressed over many cleanups. Moreover, being a
test only utility, it was not tested separately (and hence the
regression).
How about having 2 separate long double tests X86LongDoubleType and QuadPrecisionLongDoubleType? You can have them return early by testing: