But the task should be run inside a test no ? Me i want to run only one time this command. But it should be apply before every test. It a seed db via docker.

I would get all the values, then all the values from the elements , and create a boolean to use , if any of the strings differ make it return false and at the end of comparing just assert that boolean to be true/false

Thanks for taking time to respond to that . That's something I could do. Not sure how it'll be reported in the test report. I'm also considering that aspect of it.

@User If I recall correctly, you can do assertions and add a custom message at the end, so add the array of the elements that were not the same into the message and it should be good to go

That would be great starting tip for me. Thank you so much !

I found a way and made changes. All my verification are in a JS function in a separate file. I saved all the files and restarted Cypress and ran the test. It continues to run the old code instead of the updated. Not sure if there is a way to retsart cypress with clearing the cache.

I have some ideas, will probably write a blog post / make a video

Thank you so much @User

Hi. I'm trying to get e2e & components tests working side by side in a new Vite/Vue3 app. Component tests seem to be working fine (sweet!) as per https://github.com/cypress-io/cypress-component-testing-examples However for e2e I'm stuck on

TypeError: Failed to resolve module specifier "vue".

when running a basic test like

cy.visit('/')

. Via

cypress open

I'm assuming there's some devserver config I might be missing. So far I've only got this in the plugins index:

const path = require('path')
const { startDevServer } = require('@cypress/vite-dev-server')

module.exports = (on, config) => {
  on('dev-server:start', (options) => {
    return startDevServer({
      options,
      viteConfig: {
        configFile: path.resolve(__dirname, '../../vite.config.js')
      }
    })
  })

  return config
}

Thoughts/pointers?

One thing that bit me hard a couple of times is that vite resolves it's own config file. So, if your config file is `vite.config.js`/`ts`, you should remove all the vite config and have:

js
const { startDevServer } = require('@cypress/vite-dev-server')

module.exports = (on, config) => {
  on('dev-server:start', (options) => {
    return startDevServer({
      options
    })
  })

  return config
}

@User thanks for the suggestion! I've tried it but things seem to stay the same. However, to simplify things, I just cloned the exmaple app https://github.com/cypress-io/cypress-component-testing-examples/tree/main/vite-vue and made 2 small changes: 1. Added

/cypress/integrations/Basic.spec.js

js
describe('My First Test', () => {
  it('Does not do much!', () => {
    cy.visit('/')
    expect(true).to.equal(true)
  })
})

If you try to

npx cypress open

now and run

Basic.spec

you'll get a css loader error mentioning Webpack, oddly enough. So: 2. Commented out

import '../../src/main.css'

from

/cypress/support/index.js

which as I understand should only be needed for the components tests. If you run

Basic.spec

now you'll get the same error I'm having in my own app:

TypeError: Failed to resolve module specifier "vue". Relative references must start with either "/", "./", or "../".

I will investigate after lunch (in a couple hours)

cheers! 🙂

Hmm. I'm not too stoked with having to use

cypress-real-events

instead of something like

trigger

or

invoke

. Though it seems that it's an acceptable solution that a lot of developers are using. Is there something I'm not trying?

I have a request repeated twice in my test, the first time it works when i validate the xhr.response.statusCode, or xhr.response.body.isReferred. the second time when i use the same to validate, it fails. what could be the solution? sample response yielded is attached. im using cy.intercept

You need the request to run twice?

in the application it happens twice. once when i create a data and second time when i edit and submit in the same spec

in the application it happens twice. once when i create a data and second time when i edit and submit in the same spec

You can have two

cy.intercept

then. Sounds like

cy.intercept("POST", /api).as("createThing")

and

cy.intercept("PATCH", /api/).as("editThing")

I don't know if this is a best practice, though may resolve the issue here @User

Thank you. I will try this

word, lmk how it goes

picking the previous alias only. tried with both PATCH and POST

So it's the same endpoint with the same type of request? Is this a REST api?

yes same endopoint, same type of request, yes REST

ah well of course that ain't gonna work 😂 Sorry idk if I can help from here. Feel free to DM me so we don't flood this thread

thank you

@User intercept with an if statement checking whats in the body might work?

cy.wait("@rating", { timeout: 60000 }); cy.get("@rating").then((xhr: any) => { expect(xhr.statusCode).to.eq(200); const quotestatus = xhr.response.body.isReferred; cy.wrap(xhr.response.body.isReferred).as("quoteisrefBool"); });

I have the above piece of code, this works fine after the first request, the second time doesnt recognize statusCode and the other flag

I think the first line may be consuming 1st request, and the cy.get the 2nd. So maybe it should be

js
cy.wait("@rating", { timeout: 60000 }).then((xhr: any) => {
  expect(xhr.statusCode).to.eq(200);
  const quotestatus = xhr.response.body.isReferred;
  cy.wrap(xhr.response.body.isReferred).as("quoteisrefBool");
});

a 60 second timeout is quite generous too 😅 Also, I could be wrong, though i think this may be clear for you too

js
cy.wait("@rating", { timeout: 60000 }).then({ response}) => {
  expect(response.statusCode).to.eq(200);
  cy.wrap(response.body.isReferred).as("quoteisrefBool");
});