re: Testing Svelte stores and mocking dependencies VIEW POST


Can you please offer some insight into how to make the localStorage available on the global window?

I import stores into my components, but they are failing because the localstorage that hydrates the store is not available on import.

I tried creating a localStorage object from here stackoverflow.com/a/26177872/6130344 and added it to global.window.localStorage in setupGlobalJsdom() with no luck :(

I see this is available, npmjs.com/package/jasmine-local-st..., but it looks like it's for Jasmine 2, and I'm not sure if importing it into svelte.js and adding it to global.window.localStorage is just the complete wrong way to go about this.

Any suggestion?


What version of JSDOM are you using? The latest version has an implementation of localStorage ready to go, I think.

You can also use spies but I wouldn’t bother with using a package for it (although that’s what I say about everything to be fair, so ymmv 🤷‍♂️)

Here’s an example of how I used spies to test local storage in a React codebase (with Jest):



So now I need to learn Jest or does Jasmine have spies, also I guess I need to find out what spies are lol.

I'm using whatever JSDOM you had in your dependency tree. I copied them out.

Jasmine has spies - jasmine.createSpy

I’ll see if I can port across the local storage tests to Svelte a little later today.


I knocked this up just now:


Actually kind of tricky, because writing a store in the conventional Svelte way, by calling writable at the top-level, means that the store is instantiated as soon as you import the file.

That means you need a loadX function so that you can separate out the definition of the store from the loading from localStorage. This function would need to be called somewhere when your application loads, which I haven’t shown.

That means you need separate values for notLoaded and notLoggedIn, in this example.

Also, Svelte subscribe calls the callback immediately on definition, with whatever value the store currently has.

Also, I don’t call unsubcribe anywhere... which is probably fine... subscribe was likely never designed to be used outside of a component.

Another way to do this: I could have called setItem directly after calling user.set rather than using subscribe.

Btw, this doesn’t answer the question of how to set up local storage for a component that uses this store. I haven’t tried it but I’d hope in that case you could call JSDOM’s non-stubbed getItem and then ensure that loadUser is called in your beforeEach.

Let me know if this helps!


I appreciate you taking the time, I really hope this helps someone!

Here is a link to one of my custom stores:

I like them because they self hydrate from the localstorage. Also,, the value that is sent first is the correct one and not a placeholder; which means my components don't need to handle an empty value. I also don't need to call an initiate function anywhere in my app.

You are right that it seems there is no way around this in testing. I see what you have done with the user store and I like it as it works great for testing, but doesn't work for my situation as it seems localstorage doesn't get added to the window till later.

My app is a Chrome Extension, so I'm 100% sure the window will be there for my store when the app loads.

This may be one of those situations where I have to resort to manual testing!

Another thing you can try is instantiating JSDOM before you import any test files. For Jasmine, you can create a helper (which is simply an file that’s loaded) and register it in spec/support/jasmine.json.

Jest does this implicitly because it has the notion of an ”environment” in which your tests run, and the standard environment is a JSDOM environment.

I don’t really like this approach as not all test files require JSDOM, but it might solve this problem? It’s worth trying.

Would I then import the JSDOM into svelte.js? helpers don't seem to be ES6 compatible so this is causing me some syntax errors.

Oh, of course. I should have thought of that. You’ll need to take that one function, create a new file with just that, and convert import -> require. I can try it myself tomorrow

code of conduct - report abuse