amazeelabs / bdd-gatsby-cypress Goto Github PK

Thank you for taking the time to show us your End to end testing workflow with Cypress and Gatsby! I enjoyed it and I learned a lot.

Now that I have been experimenting with these workflows in my project I have thought about a few questions which would be great to get your suggestions on.
 
 

1. Do your clients have any interface for running the end to end tests or viewing the results and screenshots? Or do only developers access the tests which are run on deployment?
    
2. Can you have multiple 'Given' statements in 1 {featureName}.feature file and 1 {featureName}.js file? For example: Given a user lands on an English page.... Then test the same functionality but different expectations on a French page.
    
3. I tried to test basic a scenario where user clicking on a specific link that redirects to an external url. Cypress always fails the test, despite the screenshots show that cypress is redirected to that external url. Is there a better way to test this?
    
4. As you mentioned in the webinar, it’s not good practice to find elements using classnames or ID's, and should be written as the client would read and understand. -  In order to achieve this I am currently getting the parent div container with a class name then finding the button that contains the text that the user should see.
    

• For example: cy.get('.classname').find('button').contains('click me')

Is this the best way to do that or can it be improved?
 
5. I have used the Lagoon project before and I saw you have Percy as a package or extension to your cypress workflow.  What benefits do you gain from Percy.io?

Thanks in advance!
Rick.