FileService Mocking #14767
-
|
I'm writing code that will abstract writing my new file types away from direct FileService calls using adapters written for each type. I want to test the adapters, however, FileService appears to not be easily mocked. Any recommendations? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
|
It appears there is no good way except muddling through the code and waiting for my test mocks to break the next time Theia frontend or FileService changes. Theia seems to have many well-written pieces, but FileService isn't one. Seriously, does the FileService really have a dependency on "defaultForOSTheme" and preferences in general? |
Beta Was this translation helpful? Give feedback.
-
|
In the end, the complexity of the Aside from that, I'm wondering whether it's possible to write browser/playwright tests to test your adapters, instead of going through the hassle of trying to mock everything. |
Beta Was this translation helpful? Give feedback.
-
|
I'm thinking, when I get some time after finishing this project, that I may do some refactoring to support a bit more generic approach for FileService. Plus, it would be worthwhile to get a better overall understanding of Theia -- I'm still a newbie. Anyway, I can see that I could use some of that FileService functionality in a potential backend situation as well. And, it might be worthwhile to provide these test fixtures external to the main Theia repo that can help devs test and even better understand Theia. Dreams and wishes for now though... Thanks |
Beta Was this translation helpful? Give feedback.
In the end, the complexity of the
FileServicestems from VS Code, as we use it to support thevscode.workspace.fsAPI.Aside from that, I'm wondering whether it's possible to write browser/playwright tests to test your adapters, instead of going through the hassle of trying to mock everything.