The miniflare vitest docs have this note
The miniflare vitest docs have this note, "you must call the globalsetupMiniflareIsolatedStorage() method at the start of your tests and use the returned describe function in-place of the regular describe/suite functions imported from vitest to enable isolated storage.We're investigating ways of removing this requirement in the future, and will likely remove this function in a future release."
This makes me sad. I like my describe level to be independent of other describe level things, but I use test/it level to organize a long chain of interdependent steps (create an item, update the item in one way, update the item in another way, etc.). Right now, I can just not use
globalsetupMiniflareIsolatedStorage, but if you make it automatic later, it sounds like all of my tests will break. I'm hoping that there will be a way to control the isolation rather than have it always be on.2 Replies
Hey! 👋 Thanks for raising this. I'm definitely open to making it configurable. Would you still be interested in having isolated
describe blocks, or would you want to disable all isolation?I manually isolate my
describe blocks by generating a new id and calling getMiniflareDurableObjectState(id) at the top of every describe block. I realize that's not completely isolated but it's isolated enough because one describe block typically only needs one id. But to answer your question, sure, if you automatically had isolation at the describe block level, that would be that much better.