You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add cloud-based integration tests for filesystem serdes #710
Filesystem serdes in the JS SDK has no cloud-based test coverage, and no example at all. The only test is a co-located unit test that fully mocks the filesystem. Nothing validates the serdes against a real durable filesystem mount (Amazon S3 Files or EFS) on a deployed Lambda - the only environment where the feature is actually supported.
Proposed work
Add a filesystem serdes example under packages/aws-durable-execution-sdk-js-examples/src/examples/ and register it in examples-catalog.ts.
Add an integration test using the CloudDurableTestRunner covering ALWAYS, OVERFLOW, preview, and replay/deserialize-from-file end-to-end.
Acceptance criteria
A filesystem serdes example exists in the examples package and catalog.
CI runs at least one filesystem serdes test against a deployed Lambda backed by a real durable filesystem mount.
The test exercises write-on-first-invocation and read-on-replay through the checkpoint envelope.
#802 added the filesystem serdes examples: serde/filesystem/filesystem-serdes.ts and serde/filesystem/filesystem-serdes-overflow.ts. Both are in the examples catalog. Both use createTests, so the cloud integration suite runs them against a deployed Lambda. They cover ALWAYS mode, OVERFLOW mode and preview generation.
The examples write to a temporary directory. A test on a real EFS or S3 Files mount would mostly check whether the mount keeps the file between invocations. The storage service and the function's mount configuration provide that guarantee, not the serdes. The serdes only writes the file, records its path in the checkpoint, and reads the file from that path. The unit tests in filesystem-serdes.test.ts and the #802 examples cover that logic. So a real-mount test would add deployment setup and cost but cover no more SDK code.
Closing as completed. #860 tracks hardening of createFileSystemSerdes, so it stays open.
Activity
ParidelPooya commentedon Oct 25, 2026
#802 added the filesystem serdes examples:
serde/filesystem/filesystem-serdes.tsandserde/filesystem/filesystem-serdes-overflow.ts. Both are in the examples catalog. Both usecreateTests, so the cloud integration suite runs them against a deployed Lambda. They cover ALWAYS mode, OVERFLOW mode and preview generation.The examples write to a temporary directory. A test on a real EFS or S3 Files mount would mostly check whether the mount keeps the file between invocations. The storage service and the function's mount configuration provide that guarantee, not the serdes. The serdes only writes the file, records its path in the checkpoint, and reads the file from that path. The unit tests in
filesystem-serdes.test.tsand the #802 examples cover that logic. So a real-mount test would add deployment setup and cost but cover no more SDK code.Closing as completed. #860 tracks hardening of
createFileSystemSerdes, so it stays open.