https://cypress.io logo
Join DiscordCommunities
Powered by
# general-chat
  • s
    Cypress is really great, I ran a tech demo of it today. One suggestion I would like to put forward on documentation, is some sort of guide for people that are straight coming to end 2 end testing from no frontend testing knowledge. The biggest learning curve is understanding the assertion logic and key words. All the bits you do explain are great
  • s
    What would you suggest?
  • s
    Like why you'd do it? The kinds of assertions you might choose to write? How much to test?
  • s
    Yeah that sort of thing.
  • s
    So you have lots of visits and clicks, not enough cannot clicks, should.exist vs should(‘not.exist’), it can be confusing to clock all the terms
  • s
    Image has loaded vs css url image loaded. Intercept receipts
  • s
    I love the Best Practices page, should be a bit more prominent.
  • s
    I’m the user - who runs a Dev team most of which have 10-15 years each Dev experience, gave up on selenium testing and now have a good looking tool. The language is the biggest barrier for us. Everything else is really well documented
  • s
    That’s really helpful. So you’re new to JS?
  • s
    But in general you understand testing and the role of e2e testing?
  • s
    @salmon-monitor-78241
  • f
    @salmon-monitor-78241 You might look up Gleb Bahmutov's blog for a lot of why's and how to's. Or there are quite a few beginner level tutorials on youtube and blogs in general. Have you also found the command by command documentation? I think that is pretty great.
  • s
    Definitely not new to JS - got on board the node train early - testing or role of e2e testing. Just getting into the language of Chai and the syntax. Getting there, just bit of a need to search for the correct syntax.
  • s
    Chai will throw you for a loop the first time. Some trivia: Mocha, Chai, and Cypress’s commands are highly inspired by rspec and capybara. At that point, JS’s testing ecosystem wasn’t as mature as it is today
  • g
    I think it is all about seeing more examples, but also glance through https://docs.cypress.io/faq/questions/using-cypress-faq because it might answer some of more advanced questions
  • u
    so i'm running */smoke-test..spec.js --headless --browser chrome but getting this error
  • u
    runs no problem when i import all of them in a all-smoke-tests.spec.js
  • u
    also runs fine in the CLI
  • r
    Is it possible to run cypress on an external url ?
  • r
    thanks!
  • u
    That's bad practice. I can however use request to a url and receive the html as their docs recommend
  • s
    Hmmmm can you post an issue to GH with a reproduction? I don’t have a quick answer for you.
  • s
    Thank you, this is ace!
  • u
    which is so weird because if i run -- spec **/02.smoke-test.spec.js it works fine
  • u
    only when I run --spec ****0
  • u
    Copy code
    --spec **/*.smoke-test.spec.js
    and only that one file
  • u
    i even deleted it and then remade it
  • u
    swapped them to the numbers in front so 01.smoke-test.spec.js instead of smoke-test.01.spec.js
  • u
    fixed it by adding " " around the file name. weird since it worked fine without quotes for all the other files and even that file directly
  • u
    so I was able to get the debugger working in command prompt in my VM. these tests work fine on my local windows and local mac. so when I run the debugger it does look like the tests kick off but it seems like its an infinite loop. so much is happening i have no clue how to address this
1...456...127Latest