pactum VS Cypress

PactumJS with JSON Schema integration.

Pactum is quite powerful allowing different kind of E2E tests, you pass the base URL to make a request and assert over the response, it has more assertion functions than supertest and also supports GraphQL

You will use Strapi to build the back-end of a simple To-Do list application. Then set up PactumJS, a testing framework to create automated tests for our back-end. We will learn the basics of Strapi while creating the back-end, dive into the basics of automated testing using PactumJS and learn about making different requests and validating the responses.

Either that, or using a tool that in my opinion is more robust, like pactum

PactumJS abstracts the challenging parts to write tests in an easy and fun way and ultimately making API Integration testing super easy.

View on GitHub

In this blog post, we'll explore a Cypress test that replicates this scenario, utilizing the powerful intercept command to manipulate network requests and responses.

Recently I came across this issue while triaging some issues at Cypress. (Shout out to MattiaMalandrone for creating an issue with clear instructions for how to reproduce). After quickly replicating the issue I sought after a solution which ultimately inspired me to write this article.

While similar to Puppeteer, Cypress, and Selenium, there are some differences. Let’s find out what they are.

This questions was asked a while ago and pretty much went unanswered: https://github.com/cypress-io/cypress/issues/23677. If it doesn't work with libraries yet I will stop battling with it for now. If it doesn't work, what are you using to test libraries?

Cypress Release Notes