Our unit tests use two types of file storage which are not tied to this Git repo:
test_tasks.py and test_mailman.py rely on external websites' image URLs (see PR #45).
test_storage.py and others rely on test files which are stored in S3 buckets living under CoralNet's AWS account.
It would probably be better to tie the availability of these images to the availability of the repo if possible. Also, in the case of the S3 files, one can't update those files without having write access to the S3 buckets.
Git is known for not performing well with large files, but Git LFS could make it work:
Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like GitHub.com or GitHub Enterprise.
StephenChan
commented
11 months ago 
Our unit tests use two types of file storage which are not tied to this Git repo:
test_tasks.pyandtest_mailman.pyrely on external websites' image URLs (see PR #45).test_storage.pyand others rely on test files which are stored in S3 buckets living under CoralNet's AWS account.It would probably be better to tie the availability of these images to the availability of the repo if possible. Also, in the case of the S3 files, one can't update those files without having write access to the S3 buckets.
Git is known for not performing well with large files, but Git LFS could make it work: