https://cypress.io logo
Join Discord
Powered by
# general-chat
  • a
    This is the modal div and all its child elements
  • a
    Please share your selector (cy.get()) and cypress error log
  • a
    I’ve also tried without the then() function, without the force click, and without the window() call
  • a
    1. Remove the 
    .window()
    . If the elements related to modal appear after clicking on 
    a.prerequestedButton
    element, using then() and putting the rest of the code inside its callback function is enough. 2. I can see that your elements IDs are generated automatically by the framework using the combination of 
    modal_
    and 
    epoch time (miliseconds)
    so you should not use that ID for selector as it is changed in each test run. Use a static selector. (If you're going to write tests for this project, better to ask FE developers to add unique attributes like 
    data-cy
    for the elements)
  • f
    My biggest pet peeve nowadays is the inability to group chainers together for the purpose of retryability, as it makes composition of helper methods difficult. Are there any plans to address this?
  • a
    Maybe this one? https://cypress.tips/courses Or on PluralSight it self but maybe a little out dated: https://www.pluralsight.com/courses/cypress-end-to-end-javascript-testing
  • g
    Appreciate it! 😄
  • b
    Test Automation University has some free courses on their website (Introduction to Cypress and Advanced Cypress) https://testautomationu.applitools.com/
  • a
    1 Okey thank you! 2 Bad example from me, it doesnt work with static IDs either…
  • b
    Regarding this, do you orient your teams to always have QA-specific attributes (data-cy)? I mean what can you recommend if the project is already old and all FE attributes are already created with no QA-specific attributes?
  • m
    Hi @lemon-oyster-64925 did the email with the recording of yesterday's webinar go out yet?
  • l
    Great question! The email is scheduled to go out later today I believe. Check your inbox in the coming hours! 🙂
  • g
    Hi Cypress Community! I created Automize which is a 100% free "Selenium IDE" - like tool that can generate an entire codebase locally in Cypress. It's great for startups or people who need QA tests quickly for their projects. You can re-use events and it also works with network events. You can also use and create variables. It has a nice GUI that lets you choose exactly which selector you would like so you are never fighting the tool. Check it out -> https://automize.dev If you have any questions / concerns or feature requests feel free to dm me. Happy Testing 🙂
  • a
    Oh bad news, I'm so blind for that as I don't have access to your code and project
  • a
    Yes, This is one of the most important things I always have a discussion about with FE team lead when starting a new project or joining a new team. Actually, this is also useful for them to write Unit/Component/Integration testing. I also had this situation (Test automation for a project without unique locators) and I've started adding the locators myself by contributing to the FE project while I was writing the automation tests.
  • a
    Well done 👍 . I will take a look and try to use it.
  • l
    thx replied. same issue. I have tried yarn run cypress open npx cypress open ./node_modules/.bin/cypress open
  • l
    same port? would you mind to talk more detail? at .bashrc # set DISPLAY variable to the IP automatically assigned to WSL2 export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2; exit;}'):0.0 at terminal, I command : echo $DISPLAY 172.24.48.1:0.0 where should I modify ?Xvfb :99??export $DISPLAY=:99?? I have tried cat /etc/resolv.conf > is 172.24.48.1 echo $DISPLAY > is 172.24.48.1:0.0 export DISPLAY=172.24.48.1:0.0 export LIBGL_ALWAYS_INDIRECT=1
  • s
    hey!
  • s
    anyone around to help?
  • e
  • f
    Type 
    TestConfigOverrides
    doesn't contain the property 
    baseUrl
    , as indicated in https://docs.cypress.io/guides/references/configuration#Environment-Variables
  • f
    v10.1.0
  • f
    Nor 
    experimentalSessionAndOrigin
  • s
    So I have four assertions I've made in my main test file, I've dynamicaly passed 3 arguments to my commands class where the logic is held
  • s
    My in my main test file I have 4 chunky methods
  • s
    How can I clean this up
  • s
    So it's more compact
  • c
    I have methods such as .EachGameHasPlayNowButton(), and leave all the chunk in designated command files
  • s
    👀
1...515253...127Latest