Thanks for sharing this with us, I think that mock servers can be pretty useful for developing. I wonder how it compares to other tools for that I know of.
In the update of solid-file-client we currently use solid-auth-cli to test all fetch methods. solid-auth-cli provides a fetch method which accepts app://ls/foo/bar urls for in-memory storage of a pod, file://foo/bar urls for using the file storage as a pod, and http[s] urls for using a remote (or localhost) pod. In our case we setup a test folder in the memory/file storage and then run our tests against it.
Advantages I see compared to Molid: can programmatically create test setup. can use GET/POST/DELETE/… requests. good for unit tests
Disadvantages: requires the app to use the solid-auth-cli fetch method. some setup is nice to have (if there is interest I can extract our setup logic into a separate package. It includes a TestFolderGenerator for creating and resetting folders)
Also, I’ve recently made a post here about solid-local-pod, which does pretty much the same thing as molid as far as I see. You can run parts of your filesystem as a localhost pod, supporting GET/DELETE/POST/…, but no authentication. So I’d be interested what the differences to molid would be. I guess starting it is slightly more complicated, though I don’t think that would be an obstacle to use it.