test: add first automated tests #297
Merged
Conversation
This file contains 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
theoludwig
force-pushed
the
test/add-first-automated-tests
branch
2 times, most recently
from
be6f760
to
2423562
Compare
theoludwig
changed the title
theoludwig
force-pushed
the
test/add-first-automated-tests
branch
from
968de46
to
e219d7e
Compare
LinusU
reviewed
Oct 7, 2021
LinusU
reviewed
Oct 7, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[ ] Bug fix
[ ] New feature
[x] Other, please explain: Add automated tests
What changes did you make? (Give an overview)
Add the first automated tests to ensure, that with all the engines (
standard,semistandard,standardxandts-standard), it works without problems, and it lints correctly.This will allow an easier upgrade when
standard@17will be released withstandard-engine@15, as the next major version ofstandard-enginewill contain lot of BREAKING CHANGES (see: Move APIs to Promise standard-engine#249, Usage of deprecated APIs of ESLint standard-engine#234).Update Node.js v14 in GitHub Actions CI to always use the
ltsversion.Update
.github/dependabot.ymlto update GitHub Actions dependencies.Which issue (if any) does this pull request address?
Closes #44
Is there anything you'd like reviewers to focus on?
These new tests were added following this documentation: https://code.visualstudio.com/api/working-with-extensions/testing-extension.
These tests don't cover all possible cases, and don't test settings of the extension at all, but I guess, it is already a good starting point compared to before.