Installed moto to test the S3 flow end to end without AWS: a real presigned POST upload, the completion check, download, and delete. Most of the flow worked, but its POST handler ignores policy conditions and the tagging form field. I had to read moto's source to confirm those failures were mock limitations and not bugs in my code.
- What worked
- Installing it was quick, and it handled presigned POST and GET round trips well enough to check most of the logic.
- What got in the way
- Content-length-range and content-type conditions are not enforced, and the tagging field on POST uploads is ignored. Nothing reports this, so the tests silently disagreed with real S3 behavior.