From 9c0fce27f13fb9d02680b4f3a8a04d9529f9e853 Mon Sep 17 00:00:00 2001
From: Justin Coyne <jcoyne@justincoyne.com>
Date: Wed, 25 Jan 2023 08:22:42 -0600
Subject: [PATCH] Use a valid IIIF info id in test

See the spec at https://iiif.io/api/image/3.0/\#52-technical-properties
---
 __tests__/src/sagas/iiif.test.js | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/__tests__/src/sagas/iiif.test.js b/__tests__/src/sagas/iiif.test.js
index 2172dd663..bb6ed3722 100644
--- a/__tests__/src/sagas/iiif.test.js
+++ b/__tests__/src/sagas/iiif.test.js
@@ -98,16 +98,16 @@ describe('IIIF sagas', () => {
 
   describe('fetchInfoResponse', () => {
     it('fetches a IIIF info response', () => {
-      fetch.mockResponseOnce(JSON.stringify({ id: 'infoId' }));
+      fetch.mockResponseOnce(JSON.stringify({ id: 'http://server/prefix/infoId' }));
       const action = {
         imageResource: {},
-        infoId: 'infoId',
+        infoId: 'http://server/prefix/infoId',
       };
 
       return expectSaga(fetchInfoResponse, action)
         .put({
-          infoId: 'infoId',
-          infoJson: { id: 'infoId' },
+          infoId: 'http://server/prefix/infoId',
+          infoJson: { id: 'http://server/prefix/infoId' },
           ok: true,
           tokenServiceId: undefined,
           type: 'mirador/RECEIVE_INFO_RESPONSE',
-- 
GitLab