PhpDocSeparationTest
class PhpDocSeparationTest extends TestCase (View source)
What the serializers do with a PhpDoc: hoist it out of the entity array and into the repository under the entity's id, and put it back on the way in.
Most of these are pure array transforms and use the in-memory repository — no temp file, no lazy loading, no save() to forget. Only testDeserializationLoadsPhpDocFromStorage goes through a real file, because the thing it verifies is the round trip through one; it owns its own path. PhpDocStorageTest::testEveryPhpDocRepositoryAgreesOnBlankDocSemantics pins the two implementations to the same semantics so the cheap double can't drift from the real writer.
Methods
No description
No description
No description
No description
No description
The only test here that needs a real file: it asserts a doc survives serialize → save() → a fresh process's lazy load → deserialize, which is exactly what the cache does and what an in-memory double cannot show.
No description
Details
protected void
setUp()
No description
void
testClassPhpDocIsSeparated()
No description
void
testFunctionPhpDocIsSeparated()
No description
void
testMethodPhpDocIsSeparated()
No description
void
testPropertyPhpDocIsSeparated()
No description
void
testDeserializationLoadsPhpDocFromStorage()
The only test here that needs a real file: it asserts a doc survives serialize → save() → a fresh process's lazy load → deserialize, which is exactly what the cache does and what an in-memory double cannot show.
void
testWithoutPhpDocStoragePhpDocIsInline()
No description