---
title: "Comment by Lakhyajit Changmai on \"Testing File Upload Size Boundaries\" | Hashnode"
description: "The exact byte-boundary cases are a strong way to make this deterministic. I’d also assert that the client clears its selected-file preview and progress state a"
url: "https://hashnode.com/posts/testing-file-upload-size-boundaries/6af72c894facdfb3d0295804/comment/6af73f943b7fa79a4a2fc6e6"
---

[Discussion](https://hashnode.com/posts/testing-file-upload-size-boundaries/6af72c894facdfb3d0295804)

Comment [Testing File Upload Size Boundaries](https://hashnode.com/posts/testing-file-upload-size-boundaries/6af72c894facdfb3d0295804)

[Lakhyajit Changmai](https://hashnode.com/@lakhyajit)

[4h ago](https://hashnode.com/posts/testing-file-upload-size-boundaries/6af72c894facdfb3d0295804/comment/6af73f943b7fa79a4a2fc6e6)

The exact byte-boundary cases are a strong way to make this deterministic. I’d also assert that the client clears its selected-file preview and progress state after a 413, so a retry with a smaller file cannot reuse stale metadata. And your distinction is important: a local mock validates client behavior, while a few genuine uploads are still needed to confirm the gateway’s cap.