-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
fix: run spec tests with testutils #3017
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@@ -0,0 +1,49 @@ | |||
import { Marked } from '../lib/marked.esm.js'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So an extension package will just need to make their own version of this file to run spec tests, right?
I'm most interested in spec tests, but is there a similar capability for running unit tests?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ya, there is a getAllMarkedSpecTests()
method to get the marked specs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not using that method in marked because we want to be able to run tests that are created in PRs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here is an example PR for an extension to run all marked tests
Co-authored-by: Steven <steven@ceriously.com>
# [10.0.0](v9.1.6...v10.0.0) (2023-11-11) ### Bug Fixes * run spec tests with testutils ([#3017](#3017)) ([014d4e6](014d4e6)) ### BREAKING CHANGES * drop support for node v16
Description
use @markedjs/testutils to run tests with node test runner
BREAKING CHANGE: test runner doesn't work in node v16
Contributor
Committer
In most cases, this should be a different person than the contributor.