The following is a suggested checklist for testing by humans.

Ingest 

Test for each action 

Manifests

Pick an object that you know has been ingested via the metadata activity stream, and retrieve the manifest its unit code and CMS ID:

e.g.
https://manifests-dev.collections.yale.edu/ycba/38803 (V3)
https://manifests-dev.collections.yale.edu/v2/ycba/38803 (V2)

IIIF images

From a manifest, pick an image, construct a URL(s), and retrieve the image.

e.g. https://images-dev.collections.yale.edu/iiif/2/ycba:c5bad9c0-24f7-482c-9852-f6a554a4314a.tif/full/full/0/default.jpg (full size)
https://images-dev.collections.yale.edu/iiif/2/ycba:c5bad9c0-24f7-482c-9852-f6a554a4314a.tif/full/250,/0/default.jpg (width = 250px)

Non-IIIF contents

e.g.
https://media-dev.collections.yale.edu/print/ycba/c5bad9c0-24f7-482c-9852-f6a554a4314a.tif

Check-in viewers

Pass the manifest to a test viewer and test.

e.g.

http://spinup-000bcd.spinup.yale.edu/mirador3?manifest=https://manifests-dev.collections.yale.edu/ycba/38803 (Mirador 3, manifest V3)

http://spinup-000bcd.spinup.yale.edu/mirador3?manifest=https://manifests-dev.collections.yale.edu/v2/ycba/38803 (Mirador 3, manifest V2)

It is recommended that the units also test using additional viewers (link for Universal Viewer will be added above)

Metadata activity stream

Currently, no units implement the activity stream strictly according to the spec. Therefore instead of testing individual activities, we probably have to consider it a one-time bulk upload and only check for the consistency of CDS2 API with the source data. 

Hints for locating elements in a manifest

V3 

V2

Displaying thumbnails

Units to test displaying hundreds of thumbnails