https://cypress.io logo
Join Discord
Powered by
# general-chat
  • c
    I evaluate?
  • s
    I've never utilised this method before
  • s
    I'm pretty junior to cypress
  • s
    Here the way I did it
  • s
    Used commands class for my logic
  • s
    And passed dynamic variables
  • s
    Using. Should
  • c
    I can see what you did and the methodology could come in handy but it's a bit far from human readable, If you make use of a pom You could have something like Const icecream = { VanillaTitle : () => cy.get(div[data-text=title]).eq(0) } Then in your spec file IcecreamsPage.VanillaTitle().should('have.text', 'Vanilla') You can make the assertion a custom command too and you'd then have IcecreamPage.VanillaTitle().Contains('Vanilla')
  • s
    So I'd make a Pom file for my assertions?
  • s
    Something like
  • s
    BasketAssertions.js?
  • s
    Then import to spec file?
  • s
    Can you tell me more about the commands class? And. Contains
  • s
    How does this make it reusable
  • c
    Make a pom file for your gets Make another command.js file for your assertions Cypress.Commands.add('yourAssertionName', { prevSubject: true}, (subject) => { #example cy.wrap(subject).should(be.visibile) Return cy.wrap(subject) })
  • c
    This way in your spec file you can have something like Lobby.Banner().IsVisible().HasPlayButtonOnHover()
  • s
    I can't declare a variable if in the body of my export
  • s
    In Pom @cuddly-thailand-33926
  • c
    In your pom place your gets not your assertions
  • c
    To create seperation of conserns
  • c
    Pom's conserns is to get the component and name it
  • s
    like this?
  • c
    Hahaha yep
  • c
    Export it
  • s
    wait I can use POM like this
  • s
    where do I add my export
  • s
    wow
  • s
    can't add like that
  • c
    At the bottom after declaring the const, like for me I have Generic, Desktop and mobile So after const assertion = {} Write export default { assertion }
  • s
    ahhh got you
1...525354...127Latest