Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Tests #152

Open
reuseman opened this issue Oct 22, 2022 · 0 comments
Open

Add Tests #152

reuseman opened this issue Oct 22, 2022 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers rewrite-v2 This is an issue to solve in the rewrite of the plugin

Comments

@reuseman
Copy link
Owner

reuseman commented Oct 22, 2022

The next goal in the rewrite is to figure out how to test the plugin. A simple idea could be to have a list of markdown files that will be parsed by the plugin. But maybe something better can be done, to involve in the testing phase the interaction with the Obsidian APIs. Resource to look at
https://publish.obsidian.md/hub/04+-+Guides%2C+Workflows%2C+%26+Courses/Guides/How+to+test+plugin+code+that+uses+Obsidian+APIs

Moreover, the markdown files should be written based on the previous closed issues and the current ones.

@reuseman reuseman added the enhancement New feature or request label Oct 22, 2022
@reuseman reuseman added this to the Version 2 - Rewrite in OHM milestone Oct 22, 2022
@reuseman reuseman added the good first issue Good for newcomers label Oct 22, 2022
@reuseman reuseman added the rewrite-v2 This is an issue to solve in the rewrite of the plugin label Oct 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers rewrite-v2 This is an issue to solve in the rewrite of the plugin
Projects
Development

No branches or pull requests

1 participant