https://cypress.io logo
Join Discord
Powered by
# e2e-testing
  • a
    I guess I could wrap the results and expose it through an alias
  • a
    nope, aliases get reset after every run.... Seriously, is there any way to keep data around? I'm not going to reseed all my data on every run
  • a
    I seed data by having a 
    cy.exec
    call in a before hook -- cy.exec runs the command that seeds data to my test database.
  • a
    @User ^
  • a
    Yeah I don't use a DB, it's all graphQL, so I have to seed it from the JS files
  • a
    I've found a "pattern" that works, but it's not very elegant. The before/beforeEach hooks are very annoying as they're not scoped unfortunately
  • f
    I've got the same problem 😫 I'm on ubuntu and firefox isn't detected... And I can't start Chrome, I must use electron...
  • p
    Hi team, a quick question, is there configuration variable that I can set to slow actions in cypress?
  • p
    In Angular, it's very easy for dom elements to get de-attached, and that makes tests inconsistent and subject to fail
  • p
    I'd have to set 
    force: true
    to fix tests every once in a while and randomly, almost feels like I should just make everything forceable by default
  • f
    hi @User I was using POM pattern (which I know is not recommended). I used the same commands in the test itself. They went through okay. However I'll have to write some reusable commands as this form is a 5 page form.
  • f
    Hi Team, I added few commands to the command.js. These commands fill read the env data from cypress.json and fill some fields. My tests execute okay but it seems to add load on my macbook as Macbook fan starts as soon as the test starts running. It's quite strange. Any cues ?
  • a
    Does Cypress run everything form the support file before every single spec file? Because holy moly is it slow. Takes 1:45 minutes for 8 small tests. I seed my users/businesses/db-stuff only once, but I get the feeling it's doing it before every test, even though I have everything in a global 
    before
    hook in the support file
  • a
    Oh boy it does
  • b
    @User the support file can be confusing
  • b
    It is run "in the context of the browser" before every test
  • a
    Is there a way to just run stuff once? Cypress seems to really not want you to store anything between tests, but that's quite critical when you mock out the entire server portion 😦
  • b
    What you are looking for is something in the plugin
  • a
    Do I have access to 
    cy
    command there as well?
  • b
  • a
    or is that all just pure TS/JS?
  • a
    ok thanks, I'll take a look!
  • b
    It is pure TS/JS with some extras
  • a
    Ok that's actually nice, so I would be able to just use ES modules and store my stuff there with getters/setters?
  • b
    Yes
  • a
    Because that's been the main issue for me. Ah perfect, thanks
  • b
    but make sure you name your file .ts
  • a
    yeah 😉
  • b
    we use ts-node to make typescript work so es modules would not work in javascript
  • a
    got it
1...151617...192Latest