TLDR: Does the Obsidian team expose an e2e test suite that plugin developers can run to validate that none of the core Obsidian functionality has broken?
I recently started working on some plugins for Obsidian. I spotted that an unpublished, in-flight plugin I’m working on broke Obsidian Canvas functionality (the plugin was stealing the space keydown event from Canvas, due to a UI library I’m using). I added an e2e test and fixed it (to be more precise I directed Claude Code to add e2e test and fix it).
But it made me wonder: does the Obsidian team have an e2e suite for core functionality, or could they expose one, so plugin developers can take a dependency on it when publishing a plugin? Preferably with extension points exposed to activate a particular state prior to running the suite. In my case, that would be making the plugin pane visible before the suite runs.