Let's do this.
Upgrading one of the two modules inplace would cause regressions (e.g.. because newer versions also fail on uncaught promise rejections). […]
[…]
If we implemented something in QUnit 2.x, like QUnit.config.ignoreUncaughtRejections that you can set to false in your test runner, would that unblock UI5 from upgrading?
I'm interested in exploring this and other needs so as to help you along. In particular, so that you have access to the TAP reporter (new in QUnit 2.16.0) that would potentially give you access to a wider range of Karma alternatives in the future. Including QTap, which is currently in development.
Feel free to reply below, or reach out at https://github.com/qunitjs/qunit/issues, or in our Matrix chat channel.
[…] Some tests could not be migrated at that time and had to stay on 2.3.2. I checked this right now and it turns out this is exactly the issue you describe. Some tests relied on unhandled promise rejections as part of their error path testing.
A QUnit.config.ignoreUncaughtRejections option would help us migrating these tests to a newer QUnit version.
Let's do this.