How to integrate core Marked.js test cases into extension packages?

[calculuschild]

I don't know enough about NPM package development....

Given that Marked.js extensions are a thing now, I know how to write unit tests for the extension itself. However, is it possible to also run all of Marked.js's test cases to ensure an extension isn't breaking default functionality?

I'm looking at https://github.com/calculuschild/marked-extended-tables which completely replaces parsing of GFM tables. In addition to the new functions it adds, it should also still pass all of the table-related tests we already cover in Marked. As Marked gets updates and adds more tests to handle edge cases, the extension falls behind, and can't necessarily use the same fixes, which becomes very tedious to manually track.

Is there some best practice way I can automatically include the latest Marked test suite as part of testing the extension each time I update Marked as a dependency? I have Marked as a dev dependency, so it seems like I should be able to reuse that somehow, but testing has always been my weakness.

[UziTech]

You can get the current tests by installing the marked github repo with something like:

npm install --save-dev marked-repo@https://github.com/markedjs/marked/tarball/v9.0.3

then you will have to create a test framework that uses the files in .\node_modules\marked-repo\test\specs

[UziTech]

Here is an example of what it could look like to run marked spec tests in an extension: markedjs/marked-bidi#362

[calculuschild]

Thanks @UziTech . Your example looks promising.

I'm curious if you would be in support of a future PR that changes matchers.js to allow passing in a Marked instance?

[UziTech]

Ya my example uses jest but marked uses jasmine which is why I couldn't just use the marked matchers

[UziTech]

We could move the tests out of marked into some sort of @markedjs/testutils package so it can just be installed as a devdep and ran with passing in marked.

[calculuschild]

Yeah I wouldn't mind something like that.