Add tests to detect missing API documentation#16912
Add tests to detect missing API documentation#16912jenweber wants to merge 5 commits intoemberjs:masterfrom jenweber:docs-regression-tests
Conversation
|
I'm pretty sure To have the It should probably be an early stage ala code quality and basic tests, so that CI runs fail fast if it is going to fail. |
|
Thanks Katie! I'll try adding it into those files. I think maybe it should go before browserstack, but after the basic/code quality tests, since building the yuidocs takes a little while. |
|
Sorry, looking closer, there are two stages: basic test and additional tests, and each |
|
We may want to combine idea from this PR and #16910. This one is more thorough in that it looks at many categories, not just classitems. But the other one gives more specific feedback about which items disappeared or were added. |
|
Lol, Ed, thank you for writing that! This is what I get for not looking at the PR queue. I'm in favor of closing my PR and adding the other checks into your test. |
|
Closed in favor of #16910 |
What it does
This PR includes a test of the highest-level yuidoc json. While a passing test does not guarantee that the docs will be rendered in the api app, it should help catch things that would definitely be missing.
Why it's needed
Historically, ember.js minor releases have caused a regression in the API docs for our users of https://emberjs.com/api/ and a scramble to make a patch release.
Changes made
bin/yuidoc-tests.jspackage.jsonscripts,test:docswhich builds the docs before running tests with qunit:ember ember-cli-yuidoc qunit bin/yuidoc-tests.jsHelp plz
binthe right place for this test to go?test:docscommand run?