ember-qunit | QUnit test helpers for Ember | Addon library

Please ensure that "@glimmer/component": "^1.0.0" line exists in your package.json. Then rerun npm install or yarn install and restart ember s. This should be there if you had used ember new with Ember 3.14+, but it seems like it might be missing.

You just need to change line "typescript": "^3.7.2" -> "typescript": "~3.7.2"

Somehow your typescript got updated to 3.8, which has this issue: https://github.com/typed-ember/ember-cli-typescript/issues/1103

Not sure what your third argument (60000) is supposed to be as I am not familiar with performance.now(), but that's not a valid call to Sinon.stub() (there is no 3rd parameter). Per the documentation though, you should be able to capture the stub function and then call a method on it to indicate the desired return value:

Not sure why it was so hard to find this information, maybe bad SEO.

Yarn tells you that the npm package find-up is expecting a Node version greater or equal 8. Accordingly to your question you are using Node 6.

End of life for node 6 was on 30 April 2019. Even Node 8 not supported anymore since end of last year.

You should upgrade to a supported version of Node to resolve that issue. Node 10 and 12 are active LTS versions. Node 13 is the current latest release. You could find an overview of Node versions and their support at https://github.com/nodejs/Release.

First, some back story:

Our application utilizes a 3rd party library for metrics and another 3rd party library for feature flags. Each library has its own service but we need the metrics service to be initialized before the feature flag service can be initialized because we want to link the analytic user data to get the right feature flags for each user. The feature flag checks are done all throughout the application so a race condition arose between when a feature flag check would occur and when the analytics file was loaded in a script tag on the webpage.

Now the solution:

The reason why this error was popping up:

Ola @Divakar, thanks for your question! And Welcome to Ember

Looking at your question it seems like it could be related to an issue that we had recently in ember-data where the generators were broken. I think they were fixed in ember-data@3.11.1 but from your package.json it would seem that you have ember-data@3.11.0

If you want to update ember-data and see if the issue is still there you can run the following:

Ember testing has moved to an async/await pattern instead of using andThen and other global test helpers. That tutorial is for a fairly old version of Ember, you'll have a lot more success with a more recent guide. Even if you are not ready to update to a newer version of ember I would still recommend following the new test patterns as they are significantly easier to read and write.

If you want to test it with andThen you wouldn't need to import it as it was provided as a global, but you need to make sure your testing dependencies are correct. I would start with comparing your current package.json with the default for ember apps at that time you may need to downgrade some packages in order to get access to the old imports and global test helpers.

As @jelhan points to in the comment above, the issue here is missing test environment settings within the environment.js configuration.

To fix the UnrecognizedURLError, adding ENV.locationType = 'none' satisfies the requirements of testem.

I also replaced the other environment variables found in the linked block.

My test environment configuration now looks like this: