Upgrade to version 4.x leads to test errors
See original GitHub issueI’m trying to upgrade ember-router-scroll
from v3.3.3 to v4.x in our project. I did the necessary adjustments in the router.js
according to the README. The project starts and works as expected.
Some tests however do not run smoothly and thow the following error message:
Assertion Failed: You attempted to remove a function listener which did not exist on the instance, which means you may have attempted to remove it before it was added.
Not sure what causes the issue but it only seems to occur after the version upgrade and following necessary code changes.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Issues you may meet when upgrading Azure function app to V4
This blog will talk about some common issues you may meet when you try to upgrade your Azure function from older runtime version...
Read more >Upgrading your build from Gradle 4.x to 5.0
Read the Upgrading from 4.10 section and make any necessary changes. Try to run the project and debug any errors using the Troubleshooting...
Read more >Upgrade to Prisma 4
Prisma 4 introduces a number of breaking changes when you upgrade from an earlier Prisma version. This guide explains how this upgrade might...
Read more >Upgrading to jasmine 4.0
Although Jasmine 4.0 may still work in some of those environments, we no longer test against them and won't try to maintain compatibility...
Read more >Terraform AWS Provider Version 4 Upgrade Guide
EC2-Classic resource and data source support. Provider Version Configuration. Note. Before upgrading to version 4.0.0, upgrade to the most recent 3.X version of ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
4.0.3!
We have this error after upgrade to the new
ember-qunit#5
and@ember/test-helpers#2+
too.By quick debug I’ve noticed that destroy() method is called twice during test teardown.
Switching to
willDestroy()
method seems to be working, but I’m not sure if it is intended/proper fix.