Error: Cannot call setValue on an empty DOMWrapper. ❯ Object.get node_modules/@vue/test-utils/dist/vue-test-utils.cjs.js:1574:27 ❯ tests/unit/views/FlexiblePoolCreate.spec.js:63:28

AssertionError: expected false to be true // Object.is equality - Expected + Received - true + false ❯ tests/unit/views/FlexiblePoolCreate.spec.js:55:37

Error: Cannot call trigger on an empty DOMWrapper. ❯ Object.get node_modules/@vue/test-utils/dist/vue-test-utils.cjs.js:1574:27 ❯ tests/unit/views/FlexiblePoolCreate.spec.js:48:21

TypeError: localStorage.getItem is not a function ❯ Proxy.isValidPersisted src/stores/multiPoolCreate.js:124:38 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.setMultiPool src/stores/multiPoolCreate.js:88:16 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.provider src/views/FlexiblePoolCreate.vue:206:30 ❯ getData src/components/DataFetcher.vue:48:27 ❯ src/components/DataFetcher.vue:57:3 ❯ node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3062:40 This error originated in "tests/unit/views/FlexiblePoolCreate.spec.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "shows the correct alert when creation fails". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: localStorage.getItem is not a function ❯ Proxy.isValidPersisted src/stores/multiPoolCreate.js:124:38 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.setMultiPool src/stores/multiPoolCreate.js:88:16 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.provider src/views/FlexiblePoolCreate.vue:206:30 ❯ getData src/components/DataFetcher.vue:48:27 ❯ src/components/DataFetcher.vue:57:3 ❯ node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3062:40 This error originated in "tests/unit/views/FlexiblePoolCreate.spec.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "shows the correct alert when creation is successful". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: localStorage.getItem is not a function ❯ Proxy.isValidPersisted src/stores/multiPoolCreate.js:124:38 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.setMultiPool src/stores/multiPoolCreate.js:88:16 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.provider src/views/FlexiblePoolCreate.vue:206:30 ❯ getData src/components/DataFetcher.vue:48:27 ❯ src/components/DataFetcher.vue:57:3 ❯ node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3062:40 This error originated in "tests/unit/views/FlexiblePoolCreate.spec.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "resets the store data when called". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: localStorage.getItem is not a function ❯ Proxy.isValidPersisted src/stores/multiPoolCreate.js:124:38 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.setMultiPool src/stores/multiPoolCreate.js:88:16 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.provider src/views/FlexiblePoolCreate.vue:206:30 ❯ getData src/components/DataFetcher.vue:48:27 ❯ src/components/DataFetcher.vue:57:3 ❯ node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3062:40 This error originated in "tests/unit/views/FlexiblePoolCreate.spec.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "updates the store when pooling method is selected". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: localStorage.getItem is not a function ❯ Proxy.isValidPersisted src/stores/multiPoolCreate.js:124:38 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.setMultiPool src/stores/multiPoolCreate.js:88:16 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.provider src/views/FlexiblePoolCreate.vue:206:30 ❯ getData src/components/DataFetcher.vue:48:27 ❯ src/components/DataFetcher.vue:57:3 ❯ node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3062:40 This error originated in "tests/unit/views/FlexiblePoolCreate.spec.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "updates the store when pipeline is selected". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: localStorage.getItem is not a function ❯ Proxy.isValidPersisted src/stores/multiPoolCreate.js:124:38 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.setMultiPool src/stores/multiPoolCreate.js:88:16 ❯ Proxy.wrappedAction node_modules/pinia/dist/pinia.mjs:1400:26 ❯ Proxy.provider src/views/FlexiblePoolCreate.vue:206:30 ❯ getData src/components/DataFetcher.vue:48:27 ❯ src/components/DataFetcher.vue:57:3 ❯ node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3062:40 This error originated in "tests/unit/views/FlexiblePoolCreate.spec.js" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "has a working download link". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.