Opened 2 years ago
Last modified 15 months ago
#56250 new defect (bug)
ReferenceErrors encountered when running QUnit tests
Reported by: | desrosj | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Review | Priority: | normal |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | |
Focuses: | javascript | Cc: |
Description (last modified by )
When running QUnit tests, there are a handful of errors output:
Error: ReferenceError: QUnit is not defined at <anonymous>:130:13 at HTMLDocument.<anonymous> (<anonymous>:132:2)
Even with these errors, no tests actually fail.
The number of errors also differences between grunt qunit
(3) and grunt qunit:compiled
(6).
Change History (7)
This ticket was mentioned in Slack in #core by desrosj. View the logs.
2 years ago
This ticket was mentioned in Slack in #core by desrosj. View the logs.
2 years ago
#5
@
17 months ago
This ticket is being discussed at https://github.com/gruntjs/grunt-contrib-qunit/issues/202 in relation to a similar issue experienced in CI by ClassicPress.
#6
@
16 months ago
grunt-contrib-qunit
7.0.1 fixed this issue on the ClassicPress testing. The issues was due to a bug / feature in Puppeteer that meant that the bridge.js file in grunt-contrib-qunit
was being injected into all frames, including those created during testing by TinyMCE for example.
A conditional check ensuring that the bridge is only loaded in the top frame has removed the encountered ReferenceErrors.
Introduced in [53580].