Spec.js | Mobile device and Browser spec detection | Mobile library

You are mocking the GetTravelDatas module with an auto-mock version by calling:

It is not working because the Dialog component is not listening for the onClick event on the body, so what you need to do in this case is to find the actual element that is being clicked, observing the dom you'll find that the overlay is a div with some overlay classes on it.

You are returning a function reference to cy.get() when you call cy.get(loginPage.forgotPasswordLink). Change It to:

Apparently, I had been reading the wrong documentation for my version. The above code has two things that needed to be changed for it to work for me.

1. You don't do @use '~@angular/material' as mat;. The important line is @import '~@angular/material/theming';, which was already put in the file by the CLI.

2. It's not @include elevation(16);, it's @include mat-elevation(16);.

@@/ looks like something that gets translated into a full path during the Nuxt build.
(ref The alias Property).

Cypress has a separate build that doesn't know about this Nuxt feature. You could try to replicate it with some webpack config via a preprocessor, but another way is to have your Nuxt app put a reference to lab_model on the window object

The problem is your getData function returns undefined. Though starts an axios request in 'backround'. And your test case calls it and immediatelly proceeds to the next line (expect(login == true)).

To fix it you should make the getData function return created by axios.get promise. And add await before getData call in test case to wait for it to finish.

I know, this question is already a bit older, but I finally found a solution here. You need to attach your component with attachTo (since May 2021) to an html element. The solution looks like this:

With Use path mappings from tsconfig.json set to Always, the IDE tries to use the mappings any time the import is added. But, as "@idea-import-spec/data" is mapped to libs/data/src/index.ts that, in turn, re-exports everything from lib/data.ts, adding a mapped import to data.ts would result in a circular dependency - that's why a relative path is used. But data.spec.ts is not re-exported in barrel, so using a path mappings there looks safe

We figured it out. As you can see in our packages.json, we have a dependency on webpack. It seems angular-devkit/build-angular does as well. We believe this created the known issue of multiple webpacks colliding and causing issues. Removing our dependency on webpack fixed the issue.