Testing: To-Do List

[LanieOkorodudu]

Tick the boxes once they are addressed and merged via PR's
To do:

• Figure out a standard way to set or override the URL of the instance under test completed
• Test the content panel completed
• Test the “more information” panel completed
• Test search by page number
• Test “search within” functionality
• Test download and share button
• Test settings (switching between different locales)
• Look into testing other extensions (PDF) completed 1755
• AV
• 3D

Test structure - proposed options

• Continue with extension-base testing(OpenSeaDragon as default)
• Explore IIIF CookBook(manifest-based) testing completed 1755
• combine both approaches
  Open to suggestions on the best way to approach this.
  Hi @demiankatz, I have created this ticket with a list of things to test and added to the next sprint. When you get a chance I'd appreciate your thoughts/inputs. Please feel free to tweak, add or remove anything that doesn't look right. Thank you so much.

[demiankatz]

Thanks, @LanieOkorodudu, this all looks like a great start to me!

Regarding the question of the "extension-base testing" vs. "IIIF CookBook testing" -- I suspect we can probably find a cookbook recipe that's equivalent to the default manifest that is currently getting loaded, and if we change things, the tests will still pass (or only require minor adjustments). I think once we have a mechanism for switching the active manifest during testing, we can experiment with the possibilities!

[LanieOkorodudu]

@demiankatz, I looked through the IIIF Cookbook manifest recipes and this manifest https://iiif.io/api/cookbook/recipe/0031-bound-multivolume/manifest.json seems to be the closest manifest we can use that is equivalent to the default manifest currently being loaded.
A few of the existing tests may not fully apply though, since some behaviours like the gallery toggle and galleryViewAfterTwoUpToggle do not seem to be available in this manifest. I’ll probably also skip adding a “search within this item” test for now, since search functionality does not appear to be available here either
But I may have missed something or be looking in the wrong place, so please let me knows if you found a more suitable Cookbook manifest for these cases.

[demiankatz]

That's true, @LanieOkorodudu, the search service may not be supported by any of the cookbook recipes. In that case, we can certainly use non-cookbook recipes for tests where strictly necessary. We should just prefer the cookbook where possible because it will likely make the tests less brittle. I definitely think it would be a good idea to explicitly specify manifest URLs in all tests, though, so it's clear which manifest is being tested, and we're not dependent on which happens to be the default at the top of the list.

[LanieOkorodudu]

still working on this PR