Skip to content

docs: fix example tests#4564

Merged
straker merged 2 commits intodevelopfrom
fix-qunit
Aug 28, 2024
Merged

docs: fix example tests#4564
straker merged 2 commits intodevelopfrom
fix-qunit

Conversation

@straker
Copy link
Copy Markdown
Contributor

@straker straker commented Aug 20, 2024

When I updated #4548 to latest it caused the qunit tests to fail. Turns out that qunitjs has been deprecated and is now called just qunit, and grunt-contrib-qunit has issues if not using latest qunit. Once upgraded I was able to get the tests passing but only in headed mode. That was because puppeteer is now headless by default, so passing the ignoreDefaultArgs param and the --headless arg was causing the issue.

jest_react was also failing and after trying to fix it with it's current dependencies @dbjorge suggested it would be better to just change it over to @react/testing-library. It also means we can support react 18 in the examples too.

@straker straker requested a review from a team as a code owner August 20, 2024 17:21
@straker straker changed the title docs: fix qunit example docs: fix example tests Aug 21, 2024
@straker straker merged commit 1a03dc6 into develop Aug 28, 2024
@straker straker deleted the fix-qunit branch August 28, 2024 14:27
straker added a commit that referenced this pull request Oct 16, 2024
When I updated #4548 to latest
it caused the qunit tests to fail. Turns out that
[qunitjs](https://www.npmjs.com/package/qunitjs) has been deprecated and
is now called just `qunit`, and `grunt-contrib-qunit` [has
issues](gruntjs/grunt-contrib-qunit#209) if
not using latest qunit. Once upgraded I was able to get the tests
passing but only in headed mode. That was because puppeteer [is now
headless by
default](https://github.com/gruntjs/grunt-contrib-qunit/blob/main/docs/qunit-options.md#puppeteer),
so passing the `ignoreDefaultArgs` param and the `--headless` arg was
causing the issue.

`jest_react` was also failing and after trying to fix it with it's
current dependencies @dbjorge suggested it would be better to just
change it over to `@react/testing-library`. It also means we can support
react 18 in the examples too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants