Code for this project can be found here. Preface This post demonstrates how the values selected in the Azure pipeline menu can be used to determine which Cypress config to run. You should be a bit familiar with Azure pipelines and Yaml before you have a go at this as I…

With larger, more complex applications and infrastructure, more intricate CI pipelines with various steps and stages and so on, the need to have your Cypress tests run on different environments often arises. Typically, our integration tests run in a dedicated build step once we’ve deployed to Development and that’s that…

An issue most of us have seen! Some web-elements are dynamically generated as a result of a previous action. For example, selecting a check-box in a web-form might populate the UI with another panel or field. Often these elements similarly have a dynamically generated Class or Attribute name and no…

Reaching a higher level of automated API testing — File uploads are a hit and miss with Cypress. There are no built-in commands that handle file uploads and you typically need to get creative with jquery events or install a node package such as cypress-file-upload to try and get your files uploaded through the frontend. …

Reaching a higher level of automated API testing — Schema Validation As we query the various endpoints as part of an API we are typically given a response. This response follows a specified schema set by the developers when they built the API and is traditionally returned as JSON. There are different schemas for different endpoints and even schemas based on…