The PHPT files were all changed by a single search/replace. I assume the class name is as irrelevant as the filename and line number, which also use patterns.

That said, if it makes sense to have at least one assertion for the message including the offending class name perhaps Zend/tests/serializable_deprecation.phpt is the test in which to do so. Let me know if so.