You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-1Lines changed: 5 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,11 @@ This document describes how to make a code contribution to the repo.
55
55
- There are no unit tests for UI
56
56
- This is because svelte-testing-library is not very good, and js-dom is not a good fit for testing things like drag-and-drop.
57
57
- There are no E2E tests
58
-
- There is no easy way to write E2E tests for an Obsidian plugin, so we don't do those.
58
+
- There is no easy way to write E2E tests for an Obsidian plugin, so we don't do those.
59
+
-`fixtures/` contains ICAL, markdown files & metadata on these files for integration tests. This allows us to use real Obsidian & Dataview to produce metadata on these files instead of writing it all by hand. You can update corresponding Dataview fixtures manually:
60
+
1. Build the plugin in dev mode
61
+
2. Copy `fixture-vault` into an Obsidian vault: `cp fixture-vault <obsidian>`. If you cloned the project into a test vault, just run: `cp -r fixtures/fixture-vault/ ../../../fixtures/`
62
+
3. Open your Obsidian test vault and run the command: `Dump metadata`
0 commit comments