In this video, Clare Macrae shows us why and how Obsidian plugin developers can add automated tests to their plugins, to save time and keep bugs at bay.
You can find more information on testing Obsidian plugins at https://publish.obsidian.md/hub/04+-+...
For more information about the Obsidian Community talks, click here: https://forum.obsidian.md/t/meta-comm...
You can request topics, or even offer to host a talk or a workshop here: https://forum.obsidian.md/t/obsidian-...
You can find more information on Obsidian here: www.obsidian.md/
Timestamps:
00:00 Introduction
00:03:39 Structure of the Talk
00:04:10 Note Refactor: Demo
00:09:21 Note Refactor: Summary
00:09:37 Dataview: Demo
00:16:53 Dataview: Summary
00:17:22 Linked Data Helper: Demo
00:24:50 Linked Data Helper: Summary
00:25:16 Tasks: Demo
00:36:20 Mantra: Never trust a test until you have seen it fail
00:38:24 Refactoring code: Demo
00:45:23 Refactoring: Summary - and testing Obsidian-specific code
00:47:26 Tasks: Summary
00:47:31 Overview of automated testing: motivation, frameworks, running tests, failing tests
00:52:00 What next? For you, and for Obsidian plugins?
00:54:49 Q&A