Hey thanks for the answer! I can show you if you’d like. I was able to instrument the app using rollup/babel and istanbul plugin. The app is in single file component and it seems to be behaving very similarly to the vue example that Gleb blogged about some time ago, but it wasn’t in TS but in JS, so I wondered if TS is the reason for those weird highlights.

Hello everyone, I see that there is

cy.intercept

which would intercept those requests made by the web app, and also it can be used to stub the responses, is there a way that I can also intercept

cy.request

made by

cypress

?

do i use my IP and my VM's IP in this for auth 0?

Hey guys I am trying to do a simple login in my app, but when I login via cypress the callback kicks me right out back to the login page

The next request sets the jwt token to deleted

anyone knows why? is this a auth0 problem?

Hmm, I don't think so.

Can you give me a reproduction repo?

Sure I can! here it is https://github.com/filiphric/trelloapp-vue-vite-ts

How would you go about testing an auth flow that uses Twilio sms?

I'm not sure how to automate getting the Auth token when a randomized confirmation code is texted to a phone number.

Has anyone got experience running Cypress against firebase emulator suite in Github Actions?

You can use Twilio api's to empty all sms first then trigger the auth flow and finally call Twilio again to get the last received sms

Thank you for the response. Could you clarify what you mean by empty all sms?

To ensure that you will read the correct sms, you have to delete all messages for the phone number in test. retrieve messages :

cy.request({
    method: 'GET',
    url: `https://api.twilio.com/2010-04-01/Accounts/${accountSid}/Messages.json?PageSize=${MESSAGES_LIMIT}&To=${phoneNumber}`,
    auth: {
      username: accountSid,
      password: authToken,
    }
  })

and for each of them delete:

cy.request({
          method: 'DELETE',
          url: `https://api.twilio.com/2010-04-01/Accounts/${accountSid}/Messages/${message.sid}.json`,
          auth: {
            username: accountSid,
            password: authToken,
          }
  });

and then wait for a new incoming message

Hi Folks, How I can verify the error when I run a Cy.task that is running a SQL query?

@User I believe the real world app has a login/password and is tested with github Actions

let me check

oh sweet.

Totally confirm

ok i will take a look here

this is my snippet from my yml file

test-mode-actions just sets IS_TEST_MODE = true and then runs build

and while reviewing the run in github.. i do have this error

NEXTAUTH_URL environment variable not set

Hi, I’m doing cypress code coverage for nuxt. I implemented Istanbul and nyc but is still missing something

Some of you can recommend me a guide?

I don't think we have a guide yet.

Hey all. I am trying to build a login command within my NuxtJS application using the Nuxt Auth module. The command looks like:

js
Cypress.Commands.add('login', () => {
  const data = JSON.stringify({
    username: Cypress.env('TEST_USERNAME'),
    password: Cypress.env('TEST_USER_PASSWORD'),
  })
  cy.window().then((window) => {
    window.nuxtApp.$auth.loginWith('login', data)
  })
})

What I don't understand is this is giving me a

Xhr

request with

canceled: true

. I read that

canceled: true

occurs because I am attempting a URL change after calling my login command like:

js
cy.login()
cy.visit('http://localhost:3000/settings/info')

Should I be waiting for the login command to finish? I tried adding an alias like:

js
cy.login().as('login')
cy.wait('@login')

but Cypress didn't seem to like that...

Hi folks, I'm having a problem with the use of a "setTimetout" inside my app component. The timeout is called immediately during tests but works as expected when running the app normally. I don't discard this as a bug in my code but couldn't figure it out. Can anybody help me? The Vue component watches for changes in the session expiration date and schedule setTimeout to end the user session when due.

// ...
  watch: {
    sessionExpiration: {
      handler: 'startSessionTimer',
      immediate: true
    },
    // ...    
  },
  methods: {
    // ...
    startSessionTimer (expiration) {
      this.clearTimer();
      if (!expiration) return;

      const timeout = expiration.getTime() - Date.now();
      console.log({ expiration, now: new Date(), timeout });

      this.timeoutId = setTimeout(() => {
        console.log({ timeoutExecuted: new Date() });
        // this.alertAndSignOut();
      }, timeout);
    },
// ...

Things work OK when I run the app, but during e2e tests, the setTimeout executes immediately, even with very lengthy expiration dates.