static plugin integration tests #8
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ethan-Arrowood
force-pushed
the
static-plugin-integration-tests
branch
from
cc81567 to
6fbb055
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Work in progress.
Loose idea is to join a fixture with a test suite, each fixture will have some key variance like the first one might just be the default behavior of the plugin, and then others would have other configurations. Some suites should even test behavior like modifying files and validating that updates are immediately available.
Once we have the set of fixtures+suites, I'd like to create some script that lets a user run it locally against a running Harper instance. This script could then be invoked in a GitHub workflow matrix so we parallelize all suite execution for a reasonably fast test coverage for the static plugin.
These tests will also indirectly test key aspects of the plugin system too!