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
Right now, our S3 unit tests point to public AWS buckets, but this comes with several limitations like the inability to test writes and the inability to test authorized reads.
Instead of hosting special CI infrastructure that exposes buckets for testing, we should figure out how to spin up an instance of MinIO inside the unit test framework that creates these buckets locally. Then we should develop test coverage for the following
public read, 1MB file, 1GB file, both path/virtual hosted buckets
authorized read, 1MB file, 1GB file, both path/virtual hosted buckets
Right now, our S3 unit tests point to public AWS buckets, but this comes with several limitations like the inability to test writes and the inability to test authorized reads.
Instead of hosting special CI infrastructure that exposes buckets for testing, we should figure out how to spin up an instance of MinIO inside the unit test framework that creates these buckets locally. Then we should develop test coverage for the following
PUT
files that don't fit in a single buffer from XRootD #39 first), both path/virtual hosted bucketsThe text was updated successfully, but these errors were encountered: