Introduction In my previous post [https://dev.to/dwwhalen/using-page-objects-in-cypress-co9] we installed Cypress, which also installed a number of Cypress sample tests. These sample tests use the Mocha syntax. In this post I'm going to talk about how to define your tests with feature files instead of Mocha. The examples
Introduction Page Objects is a pattern in test automation that allow the automation engineer to encapsulate the data and methods used to support automation of a page. Typically each page of the application will have an automation class that contains data, methods, and locators needed for automation of that page.
QA teams can be responsible for a variety of automated test types, including UI, API, performance, and security tests. Many times, I see these automated tests in a code repository that is separate from the application code repository. Why is this a bad idea?## 1. Encourages waterfall behavior In this
When building a QA test automation framework, it's critical to define the strategy for dealing with test data. For example, what’s wrong with this scenario? Given the user successfully logs into registration system When the user searches for course number “ALG-4316” Then the course is displayed And the course