Carter Capocaccia.
Husband. Father. Developer.
Using Cypress and Github Actions to Build an Automation Platform. Its easier than you think.
More Stories
Quick snippets - Stop forcing it!
Forcing user behavior in automated tests can garner false negative results. A test will pass when in reality, it shouldnt! In this example I review how a Cypress test can fail even when the applicaiton is not functional.
Quick Snippets - Validate all page links
Broken links can lead to an exteremely frustrating user experience and checking each link manually is a time consuming process. Using Cypress, we can automate this entire process and ensure all of our links perfom as expected.
Data driven test generation - Parallelizing large data sets.
A problem arises in test automation when repetitive tasks needs to be performed on large data sets. In this post, I discuss how we can level up from a forEach loop and use Node to unlock parallelization.
Accessibility driven test flows using Cypress Testing Library.
Accessibility concerns are often overlooked on web apps. As QE Engineers, what can we do to make sure that our tests interact with the application similarly to how users would?
QA and CI/CD with Vercel and GitHub Actions
Want to see the QA tools and workflows I use for this site? Check it out here.
Effective DOM selector patterns. Interact like a user.
There are many ways now to retrieve a DOM node during a test. In this article I rank a few of the more popular methods and provide my opinion as to which ones are viable solutions.
Easy mocking of API Requests in Cypress with Mock Service Worker.
Mock Service Worker is a single tool we can use to mock API requests in unit tests, end-to-end tests, and our application. In this example, Cypress starts the worker on its own.
Cypress testing CMS configured layouts.
When testing CMS configured layouts, you have an edge. In this post, I discuss how I create tests for CMS configured layouts.
